-
Notifications
You must be signed in to change notification settings - Fork 55
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
Unable to start containers at boot time #2
Comments
Docker API creation starts after network endpoinds get up. I think network must store its options (bridge name and ipv6 enable option) independently from docker. |
Apologies for the late response! I'll look into this with the Go version I'm back to working on. |
@devplayer0 Hi there! Is there any workaround using a newer version or slightly different configuration? |
I have the plugin installed and working correctly, for manually started containers. However, I have one container set to restart=always, which means it gets started at bootup. When docker attempts this it fails after 60 seconds with the error:
UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)
The revelent section from the syslog:
This seems to suggest it's trying to access the Docker API before it's been made available. I'm not sure if that's a setup issue on my side or not, I can't see any options to delay starting containers until the API is available.
The text was updated successfully, but these errors were encountered: