Skip to content
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

snap install-ed docker daemon fails to start with "no available network" #63

Open
lestephane opened this issue Feb 28, 2022 · 3 comments

Comments

@lestephane
Copy link

lestephane commented Feb 28, 2022

Feb 28 10:59:57 localhost docker.dockerd[32334]: failed to start daemon: Error initializing network controller:
 list bridge addresses failed: PredefinedLocalScopeDefaultNetworks List: [172.17.0.0/16 172.18.0.0/16 
172.19.0.0/16 172.20.0.0/16 172.21.0.0/16 172.22.0.0/16 172.23.0.0/16 172.24.0.0/16 172.25.0.0/16 
172.26.0.0/16 172.27.0.0/16 172.28.0.0/16 172.29.0.0/16 172.30.0.0/16 172.31.0.0/16 192.168.0.0/20 
192.168.16.0/20 192.168.32.0/20 192.168.48.0/20 192.168.64.0/20 192.168.80.0/20 192.168.96.0/20 
192.168.112.0/20 192.168.128.0/20 192.168.144.0/20 192.168.160.0/20 192.168.176.0/20 192.168.192.0/20 
192.168.208.0/20 192.168.224.0/20 192.168.240.0/20]: no available network
@lestephane lestephane changed the title snap install-led docker daemon fails to start with "no available network" snap install-ed docker daemon fails to start with "no available network" Feb 28, 2022
@lestephane
Copy link
Author

I found this, which refers to a docker0 interface which I don't have. I would have expected the snap install to create that interface if needed.

@tianon
Copy link
Contributor

tianon commented Feb 28, 2022

Interesting -- this does normally get created automatically. Do you have any more details about your environment that might help us figure out what's going wrong?

@lestephane
Copy link
Author

Unfortunately not, now I see a docker0, and the problem has disappeared. I tried many different steps, hard to tell which one solved the problem. I did apt-get install bridge-utils for example, because some blogs explaining docker0 manual creation mentioning it. I thought maybe the snap install logic needed it to create docker0 on my behalf. But I never did create the docker0 interface manually myself. Eventually, docker0 got created, and the docker daemon started without the error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants