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

'Overlay not found...ensure kenel new enough' Error on Arch Linux #14489

Closed
toddleo opened this issue Jul 9, 2015 · 8 comments
Closed

'Overlay not found...ensure kenel new enough' Error on Arch Linux #14489

toddleo opened this issue Jul 9, 2015 · 8 comments

Comments

@toddleo
Copy link

toddleo commented Jul 9, 2015

Hi, I'm trying to run a docker image on my Arch Linux machine, however I cannot pull the image from Docker Registry, and as I dig into it I found the docker daemon failed to start:

> sudo docker pull ubuntu
Cannot connect to the Docker daemon. Is 'docker -d' running on this host?
> sudo docker -d
INFO[0000] Listening for HTTP on unix (/var/run/docker.sock) 
ERRO[0000] 'overlay' not found as a supported filesystem on this host. Please ensure kernel is new enough and has overlay support loaded. 
WARN[0000] Running modprobe bridge nf_nat failed with message: , error: exit status 1 
FATA[0000] Error starting daemon: Error initializing network controller: Error creating default "bridge" network: operation not supported

docker version:
Client version: 1.7.0
Client API version: 1.19
Go version (client): go1.4.2
Git commit (client): 0baf609
OS/Arch (client): linux/amd64
Cannot connect to the Docker daemon. Is 'docker -d' running on this host?
docker info: Cannot connect to the Docker daemon. Is 'docker -d' running on this host?
uname -r: 4.0.6-1-ARCH
Any thoughts?

@GordonTheTurtle
Copy link

Hi!

Please read this important information about creating issues.

If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.

If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.

This is an automated, informational response.

Thank you.

For more information about reporting issues, see https://github.com/docker/docker/blob/master/CONTRIBUTING.md#reporting-other-issues


BUG REPORT INFORMATION

Use the commands below to provide key information from your environment:

docker version:
docker info:
uname -a:

Provide additional environment details (AWS, VirtualBox, physical, etc.):

List the steps to reproduce the issue:
1.
2.
3.

Describe the results you received:

Describe the results you expected:

Provide additional info you think is important:

----------END REPORT ---------

#ENEEDMOREINFO

@cpuguy83
Copy link
Member

cpuguy83 commented Jul 9, 2015

The overlay kernel module is not loaded, and as such cannot be used.
Are you using a custom kernel? Is the kernel compiled with overlay support?

Closing since this is not a Docker issue.

@cpuguy83 cpuguy83 closed this as completed Jul 9, 2015
@toddleo
Copy link
Author

toddleo commented Jul 14, 2015

Hi cpuguy83,
no, the kernel is not customized, it comes with Arch Linux.

@vanga
Copy link

vanga commented Jul 25, 2015

@toddleo did you get it to work? what's the solution for this? I get the same error on ArchLinux

Thanks

@vanga
Copy link

vanga commented Jul 25, 2015

though, my error is slightly different
My Kernel version is 4.0.x

INFO[0000] Listening for HTTP on unix (/var/run/docker.sock) 
ERRO[0000] 'overlay' not found as a supported filesystem on this host. Please ensure kernel is new enough and has overlay support loaded. 
WARN[0000] Running modprobe bridge nf_nat failed with message: , error: exit status 1 
FATA[0000] Error starting daemon: Error initializing network controller: Error creating default "bridge" network: package not installed 

@toddleo
Copy link
Author

toddleo commented Jul 27, 2015

@vanga: no I haven't got it right yet, decided to deploy on physical machine instead of using docker, due to our strict time limit. :D

@benjah1
Copy link

benjah1 commented Sep 15, 2015

@toddleo @vanga have you try the --privileged flag?

docker-library/docker#5

@hut8
Copy link

hut8 commented Oct 30, 2015

I just had the same issue a few minutes ago on Arch. The official Docker package for Arch does install bridge-utils, but then you need to reboot to load it.

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

6 participants