-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
Apparmor "no such file or directory" #403
Comments
Does the same thing happen if you try to |
No, I can start the container normally with docker just fine. |
Actually, scratch that last reply. I can use docker to start the same base image, but I can't start the image created by fig:
|
I notice that the original example says it's recreating. What happens if you |
Thanks. But no change.
Docker was in a bit of a mess when I started this (confusion about versions and Ubuntu packages). Is there something else I can do to create a clean slate? |
More digging here reveals that it breaks in this way if I declare volumes, and not if I don't. I see this in the fig.yml docs: "Mapping local volumes is currently unsupported on boot2docker." But I have no idea what that means. The workaround suggested is to "use docker-osx", but I'm on an Ubuntu host, so that doesn't help. If I can't declare local volumes it's kind of bust. |
Volumes should work from a linux host, that warning is just for osx users I think (might need some clarification, it seems to assume that most people are on osx). It may be related to the base image you're using? Can you reproduce with |
Yes, that is still broken. Here's the fig.yml:
|
Aha. User error: the volumes are an array (even if single valued). That fig.yml is still illegal for some reason when I fix it (I can't bind to "."), but it's a different error at least. Why can't I bind to "."? |
I believe they need to be absolute paths (https://docs.docker.com/userguide/dockervolumes/) |
OK, I guess I get work around that using "${PWD}". IMO part of the value of fig should be to avoid that kind of limitation invisibly. Now let's see if I can do something really useful with it... As far as the original issue goes, maybe fig should validate its YAML better to avoid cryptic errors from a different layer? |
Definitely #129 is the issue for that. |
Mounting to a relative path inside the container feels really weird to me. What were you trying to do? |
The opposite (duh!). Off by one error means you mount in the wrong direction. Sorry for the noise (it was unrelated to the original problem anyway). |
#129 seems like the right place to discuss the validation issue |
Note that I had this same issue and it turned out to be that fig will complain with that message if volumes are not listed as an array. Might be a good idea if fig explained that it was an error in the fig syntax.
bad.
good |
I have the save issue on a very simple yml:
on
Error message:
My host is Ubuntu precise inside a Vagrant box:
Any idea? |
Same here: cfg2:
build: .
ports:
- "3000:3000"
- "2222:22" In ubuntu 14.04 |
My problem was solved with the next steps:
I think the problem was than I used a image generated with docker 1.4. |
This change to docker claims to have fixed the problem: moby/moby#6180, but it's still failing for me.
The text was updated successfully, but these errors were encountered: