Open vlastikcz opened 1 day ago
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.
Are you by some chance using portainer to deploy the compose file?
Hello,
no, pure docker compose -f docker-compose.yaml up -d
. It's an older (months old) instance which worked fine before. The failure started after docker compose pull
yesterday.
I run docker compose pull
manually on approx. weekly basis. I have not changed anything else.
services-web@rpi4:~/rpi-home/docker/web$ docker compose version
Docker Compose version v2.29.7
services-web@rpi4:~/rpi-home/docker/web$ docker version
Client: Docker Engine - Community
Version: 27.3.1
API version: 1.47
Go version: go1.22.7
Git commit: ce12230
Built: Fri Sep 20 11:41:08 2024
OS/Arch: linux/arm64
Context: default
Server: Docker Engine - Community
Engine:
Version: 27.3.1
API version: 1.47 (minimum version 1.24)
Go version: go1.22.7
Git commit: 41ca978
Built: Fri Sep 20 11:41:08 2024
OS/Arch: linux/arm64
Experimental: false
containerd:
Version: 1.7.22
GitCommit: 7f7fdf5fed64eb6a7caf99b3e12efcf9d60e311c
runc:
Version: 1.1.14
GitCommit: v1.1.14-0-g2c9f560
docker-init:
Version: 0.19.0
GitCommit: de40ad0
Is there an existing issue for this?
Current Behavior
Container does not start because of an python error:
Expected Behavior
Container can be started (as it did with previous versions)
Steps To Reproduce
Environment
CPU architecture
x86-64
Docker creation
Container logs