Is there an existing issue for this?
Current Behavior
Hi, after the latest pull to the current version, the container can't be started, stopped, or removed without first restarting the Docker daemon. Has anyone had the same problem? The problem persists even with the previous image.
Expected Behavior
No response
Steps To Reproduce
Last release, with Docker Compose on Debian 12 and Openmediavault.
Environment
- OS:Debian 12
- How docker service was installed: compose
CPU architecture
x86-64
Docker creation
Container logs
Is there an existing issue for this?
Current Behavior
Hi, after the latest pull to the current version, the container can't be started, stopped, or removed without first restarting the Docker daemon. Has anyone had the same problem? The problem persists even with the previous image.
Expected Behavior
No response
Steps To Reproduce
Last release, with Docker Compose on Debian 12 and Openmediavault.
Environment
CPU architecture
x86-64
Docker creation
Container logs