Replies: 1 comment 4 replies
-
Thanks for reporting! I recall we had a similar issue with another endpoint (?) where cancelling the context cancelled the process;
Actually wondering now if that one would also resolve the issue you're seeing; what version of docker are you running? (I see that patch was backported to the 24.0.3 patch release) |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello everyone,
I'm currently facing a unique situation. We're binding the Docker Unix socket into a container (-v "/var/run/docker.sock:/var/run/docker.sock") and making certain API functions (container restart / start / stop) available to a WebApp through an nginx server. This allows us to start, stop, and restart all installed containers via the WebApp.
However, since updating to version 24.X.X, the restart function hasn't been working properly. When the container with the nginx server is restarted, it stops but doesn't start up again. After some investigation, I found that with this commit (def549c), the "context" of the API request is passed to the containerStart() functions. Since the request originates from the container that was just stopped, the connection closes, and the containerStart() function throws an error, indicating an incorrect context. As a result, the container stops but doesn't restart.
I understand that this is a very specific scenario, but I cannot install an nginx server on the host. So, I wanted to ask if anyone knows another way to utilize these functions (start, stop, restart of all containers) within a container. For now, as a temporary fix, we'll continue using version 23.x.x, but this doesn't seem like a sustainable solution to me.
Beta Was this translation helpful? Give feedback.
All reactions