Docker Compose freezing with Podman during up/down #10922
Assignees
Labels
In Progress
This issue is actively being worked by the assignee, please do not work on this at this time.
kind/bug
Categorizes issue or PR as related to a bug.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
Comments
|
docker-compose file? |
|
same issue here (same distro/podman version), here is the file: version: "3.7"
services:
db:
container_name: postgres
restart: always
image: postgres:10.5-alpine
environment:
POSTGRES_USER: "user"
POSTGRES_PASSWORD: "password" # TODO: Change this
POSTGRES_DB: "user"
MAX_CONNECTIONS: 500 # TODO: do not hard code use proper bounce
volumes:
- pgdata:/var/lib/postgresql/data
ports:
- "5432:5432"
cache:
container_name: cache
restart: always
image: redis:4.0-alpine
ports:
- "6379:6379"
volumes:
pgdata:
|
|
Here are some logs that might be relevant: |
|
ish! thanks |
|
Adding to my previous comment, the freezing happens only with rootless Podman. Preceding the commands with sudo fixes the problem. For example, |
|
Despite the aforementioned, Podman Compose still works with Podman. |
|
I know how to fix this. I will work on it tomorrow. |
|
Seems like restarting user-level podman socket remediates this. |
Luap99
added
the
In Progress
Luap99
added a commit
to Luap99/libpod
that referenced
this issue
Jul 15, 2021
There was an race condition when calling `GetRootlessCNINetNs()`. It created the rootless cni directory before it got locked. Therefore another process could have called cleanup and removed this directory before it was used resulting in errors. The lockfile got moved into the XDG_RUNTIME_DIR directory to prevent a panic when the parent dir was removed by cleanup. Fixes containers#10930 Fixes containers#10922 To make this even more robust `GetRootlessCNINetNs()` will now return locked. This guarantees that we can run `Do()` after `GetRootlessCNINetNs()` before another process could have called `Cleanup()` in between. [NO TESTS NEEDED] CI is flaking, hopefully this will fix it. Signed-off-by: Paul Holzinger <[email protected]>
Luap99
added a commit
to Luap99/libpod
that referenced
this issue
Jul 15, 2021
There was an race condition when calling `GetRootlessCNINetNs()`. It created the rootless cni directory before it got locked. Therefore another process could have called cleanup and removed this directory before it was used resulting in errors. The lockfile got moved into the XDG_RUNTIME_DIR directory to prevent a panic when the parent dir was removed by cleanup. Fixes containers#10930 Fixes containers#10922 To make this even more robust `GetRootlessCNINetNs()` will now return locked. This guarantees that we can run `Do()` after `GetRootlessCNINetNs()` before another process could have called `Cleanup()` in between. [NO TESTS NEEDED] CI is flaking, hopefully this will fix it. Signed-off-by: Paul Holzinger <[email protected]>
github-actions
bot
added
the
locked - please file new issue/PR
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
When starting a project with docker-compose (version 1.29.2), the command freezes and then gives a timeout. Podman socket is active (
systemctl --user status podman.sockis OK)Start podman socket
Run docker-compose up
Describe the results you received:
Describe the results you expected:
Additional information you deem important (e.g. issue happens only occasionally):
Output of
podman version:Output of
podman info --debug:Package info (e.g. output of
rpm -q podmanorapt list podman):Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/master/troubleshooting.md)
Yes
Additional environment details (AWS, VirtualBox, physical, etc.):
The text was updated successfully, but these errors were encountered: