-
Notifications
You must be signed in to change notification settings - Fork 86
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to update store for object type *libnetwork.sbState: timeout #300
Comments
ping @ctelfer @fcrisciani - was anything around this fixed in a more recent version of Docker? |
AFAICT, the only file that references sbState is |
Are you still seeing this issue on a current version of docker? |
@thaJeztah HI i see this error i am in the Docker version 27.1.2, build d01f264 Docker version 27.1.2, build d01f264 Server: |
Sorry @thaJeztah , I missed this comment completely. It's been a while since I haven't run the types of workflows on EC2 instances that would cause this error to happen. Since there have been many releases in the meantime and nobody else complaining about this issue, I think we should close it 🙂 . @noamgreen If you'd like, please go ahead and open a separate issue, as I don't think the root causes of these two are related. |
Expected behavior
Container starts normally
Actual behavior
Container fails to start with message:
Steps to reproduce the behavior
It seems to be happening randomly.
There are different workflows that are ran and they use different images with slightly different configuration (the only difference is the command they execute). However, the images and commands themselves should not be the problem, since they work 99% of the time. They all have the following in common:
Here are the full logs:
We can see here that there were 5 containers that were created successfully. 4 of them each failed to start once (500 error code on the client) and then succeeded and one of them failed to start the first time with 500 error code and then failed to start 5 times with 403.
Here is the filtered version of the above logs with only the relevant parts:
Output of
docker version
:Output of
docker info
:It's not the exact machine on which this error occurred, but one with same configuration, i.e. difference is in number of containers and images, but those are also quite similar.
Additional environment details (AWS, VirtualBox, physical, etc.)
AWS box
Related issues
#235 is similar, but not sure if related
The text was updated successfully, but these errors were encountered: