-
Notifications
You must be signed in to change notification settings - Fork 9
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
Files in some directories end up owned by root, causing test failures #24
Comments
Steps to reproduce:
where the pertinent bit is
|
Line 107 in 691f0ef
... Line 140 in 691f0ef
... chaste-docker/scripts/build_chaste.sh Line 27 in 691f0ef
so don't see why it wouldn't end up owned by the chaste user... something to do with the volume? |
In terms of UID it looks exactly the same:
where 0 maps to root both locally and in the docker |
Not too surprisingly, starting from chaste/base and running |
Using
has the same permissions issue as release |
Have now tried it on an ubuntu (running docker inside of virtualbox...) and it does exactly the same: the files in Working hypothesis: The Dockerfile specifies that it should be root, and whatever is being done afterwards to make it work in docker desktop fixes this |
I think I've found it: Lines 143 to 162 in 340edc5
These lines create a whole new image, and the Solution is just to add another
inside the |
Nope that's not it! When I build a new one locally it works fine Will wait until the new images become available and then try again |
Hi @MichaelClerx, thanks for the detailed investigations. The new |
Interestingly, the
License says 2025, so looks like the new image to me Other folders look OK, except for the projects folder because it's a symlink to a folder inside |
On fedora, using docker from the terminal.
Following first instruction here: https://github.com/Chaste/chaste-docker?tab=readme-ov-file#recommended-using-a-pre-built-image
docker run --init -it --rm -v chaste_data:/home/chaste chaste/release
It sets things up alright, but some of the files in the volume it creates are owned by root, causing test failures
The text was updated successfully, but these errors were encountered: