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

aufs test_add:246:docker[973] /var/lib/docker/ is overlapped #3668

Closed
coderlol opened this issue Jan 20, 2014 · 6 comments
Closed

aufs test_add:246:docker[973] /var/lib/docker/ is overlapped #3668

coderlol opened this issue Jan 20, 2014 · 6 comments

Comments

@coderlol
Copy link

Docker version: 0.7.5

I have 2 images: tomcat and jenkins. jenkins is based on tomcat

The tomcat image sets up tomcat, supervisor, etc. Tomcat is installed to /opt/tomcat
The jenkins image is "from" tomcat and add the jenkins.war file to the tomcat /opt/tomcat/webapps dir.

Building jenkins give the following message:
aufs test_add:246:docker[973] /var/lib/docker/ is overlapped

What gives? If I do not add the jenkins.war file to /opt/tomcat/webapps, then I do not ge the "is overlapped" message.

Can the message be safely ignored?

@unclejack
Copy link
Contributor

@coderlol As far as I've seen, that warning had no side effect and it's also being printed on my system running Docker on AUFS.

I'll close this issue now. Please report back if you run into problems and you think they might be somehow associated with those warnings.

@damm
Copy link

damm commented Mar 6, 2014

+1 for this error; unfortunately it's actually blocking me.

I'm having containers fail silently during build on this.

Step 5 : RUN ./installer --dont-install-useful-gems --no-tcmalloc -a /usr
 ---> Running in 251cb17402ab

I'll try and figure out more information and open a new issue on this.

@mcobzarenco
Copy link

+1 I have the same problem as @damm

@damm
Copy link

damm commented Jul 21, 2014

@mcobzarenco you should try the btrfs storage engine (I adopted coreos) to deploy Docker with as I just found building with aufs to be a bit too buggy (too much of a time waste)

@mcobzarenco
Copy link

@damm Thanks for the suggestion, I'll give it a try today.

@coladict
Copy link

While our server's RAID was down we did not have this warning. I stopped all containers, synced the secondary drive and when I started the containers again, I started getting those warnings. It happens when they start on every boot, but not on every container. I can probably check which ones do 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

5 participants