Open elFarto opened 4 years ago
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. I try to store options to file and now containers start at boot time without any problems. Also now plugin filling in-file option from the docker option on endpoint creation, so just restart containers after update plugin and everything must work like a charm.
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.