-
Notifications
You must be signed in to change notification settings - Fork 26
Error checking context on docker build #8
Comments
I'd say it's an expected behavior.
An Apparmor denial popups in /var/log/syslog as well
I would recommend Here are the steps to reproduce the above "issue" and run docker build in a proper way under the confinement mode.
I hope this's helpful for you. P.S |
Worked great, thanks! |
I'm using a different approach. sudo docker run -ti --rm --name docker -v $(pwd)/source:/source -v /var/run/docker.sock:/var/run/docker.sock rpi-docker /bin/sh Im running Ubuntu Core 16. |
This issue can be solved entirely by simply installing docker in devmode, like so: Also, it is worth pointing out that the instructions listed at the snapcraft site are wrong. Particularly, the section:
Had absolutely no effect for me. |
got it working using @egee-irl answer ! thank you |
Is this issue a result of installing docker using snap? I have a fresh ubuntu 18.04 LTS install and installed Docker using |
Here worked great, thanks!!! |
Can confirm that placing the dockerfile within the homedir tree did not work. It seems the docker snap is broken. |
Same kind of issues here with docker snap. Running the very simple
Fails with error
Relevant line in
Apparmor denied ? @egee-irl Ubuntu Bionic packages at |
Creating a UNIX GROUP "docker" and adding the $USER has worked for me. |
@adglkh, worked great, thanks! |
@rickrain If you are using docker on ubuntu from snap follow. $ sudo snap install docker Connect the docker:home plug as it's not auto-connected by default: $ sudo snap connect docker:home Create and join the docker group. $ sudo addgroup --system docker $ sudo snap disable docker |
This allows root to read from non-root owned folders. This specifically should fix docker-archive#8
Hi folks, I've released a new version of the docker snap to edge and beta channels that uses a new feature with the home plug that allows root to read non-root files. You can try this out by refreshing the snap to the edge channel for testing:
And then attempt to build a Dockerfile owned by your user somewhere:
And it should work.
Update 2: This feature has been approved for use by the docker snap and is available in the edge and beta channels. You can try it out with the above. It should land into stable shortly. |
Closing all issues and pull requests since this repo is getting archived (see notice at the top of README). |
Running
sudo docker build -t <image> .
in the context of/home/$USER
, but getting the following error (where$USER
is the actual username):Running the following Snap version:
Some more system details:
The text was updated successfully, but these errors were encountered: