-
Notifications
You must be signed in to change notification settings - Fork 11
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
Docker setup fails with permissions error #237
Comments
Here's what I ran:
This sequence of commands puts me into a Docker image running Arthur. Here's the state of
(The additional commit on Please be sure to be on the latest version as shown above. "permission denied" may have popped up during development on To debug, please re-run the
and let me know what error messages show up. |
Will do, thanks @tvogels01 ! |
Some more info: First, the 'debug probe' commands on the fresh image, no volumes linked:
Works as expected. Then, the
Ok, fair enough, I'll set one (to an existing directory on my machine):
With 'probes':
So I suppose |
I'll have to dig in to Docker volumes to see what might cause this issue. For me, the owner of To unblock you, I'd suggest that you switch into your warehouse directory before starting arthur. The reason is that this will put the image into "standalone" mode which means it won't try to run Here's what happens on my laptop:
Also, I just realized that directories get mounted multiple times in your setup. Maybe that's part of the issue? Please create a new directory above the config so that it's parallel to this repo.
Notice how
Assuming that the configuration directory is now in |
Running from the 'warehouse' directory and not from arthur source directory seems wise. I also forgot the sibling setup is 'repo' then 'config' adjacent to e.g. 'sources'. Added that layer. In fact I did a Perhaps I have some global docker settings or version info I don't know about. Does classic the |
Using a virtual env might work but I haven't tested in a while. I don't see why it wouldn't. Here's what the permissions should look like:
Note how the user stays In the end, this is the directory structure that you're aiming for:
For now, what happens if you simply comment out the line |
Please take try out: Allow read-only source directory #242 When the Docker image is created, an |
Summary
After a fresh install, attempted to run arthur:
Details
Prior steps were only
git clone
and./bin/build_arthur.sh
Propose label: Bug, maybe documentation bug?
The text was updated successfully, but these errors were encountered: