Woodpecker is a simple, yet powerful CI/CD engine with great extensibility.
4.07k
stars
353
forks
source link
Woodpecker agent fails to see finish on podman user socket if journald is set to MaxLevelStore=warning #2035
Closed
waffshappen closed 1 year ago
Component
agent
Describe the bug
When running woodpecker agent as follows:
podman run -d --security-opt="label=disable" --tmpfs /tmp --cgroups=split --restart=no --label io.containers.autoupdate=registry --hostname woodpeckeragent --name woodpeckeragent --tz Europe/Berlin -e DOCKER_HOST="unix:///run/user/1001/podman/podman.sock" -e WOODPECKER_SERVER=[..] -e WOODPECKER_AGENT_SECRET=[..] -e WOODPECKER_MAX_PROCS=2 -e WOODPECKER_KEEPALIVE_TIME=60s -v /run/user/1001/podman/podman.sock:/run/user/1001/podman/podman.sock --cpu-shares=128 --memory=2G docker.io/woodpeckerci/woodpecker-agent:latest
And with (this doesnt change the result, was an attempt)
And
woodpecker agent never realizes when a container is finished and will be stuck waiting forever.
If MaxLevelStore is set to default it will work immediately.
System Info
Additional context
No response
Validations
next
version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]