Skip to content

Commit 6e7bb36

Browse files
authored
Add podman timeout info to faq
1 parent be0c769 commit 6e7bb36

1 file changed

Lines changed: 15 additions & 0 deletions

File tree

README.md

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -332,6 +332,21 @@ etc
332332
333333
Yes, tested against podman 4 and 5, in rootless and rootful modes, on macos and linux.
334334
335+
Note you probably will need to update the podman socket timeout, to avoid a disagreement between the docker-java api and podman..
336+
_(as per https://github.com/testcontainers/testcontainers-java/issues/7310 )_
337+
338+
- Linux:
339+
```bash
340+
sudo mkdir -p /etc/containers/containers.conf.d
341+
printf "[engine]\nservice_timeout=91\n" | sudo tee -a /etc/containers/containers.conf.d/service-timeout.conf
342+
```
343+
344+
- Mac:
345+
```bash
346+
echo 'mkdir -p /etc/containers/containers.conf.d && printf "[engine]\nservice_timeout=91\n" > /etc/containers/containers.conf.d/service-timeout.conf && systemctl restart podman.socket' | podman machine ssh --username root --
347+
```
348+
349+
335350
**Does this work on Windows?:**
336351
337352
Yes.. it's supposed to! (although the automated test suite on github is unable to run as the runners don't support nested virtualization)

0 commit comments

Comments
 (0)