You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What is very strange is that other subrepos like https://github.com/apache/brooklyn-libraryworks perfectly fine with the same config. In any case, the code is actually compiled properly in each target folder . It seems that there is an issue when the file/folder to be created is at the root of the build folder.
It definitely looks similar to #83.
The text was updated successfully, but these errors were encountered:
You try to map ${HOME}/.m2 to container's /var/maven/.m2
please check if you have ${HOME}/.m2 directory already created and owned by 501:20 before trying to run container. If You try to run container and directory not exists, it will be created by Docker as root.
I'm trying to using this Docker image to build all Apache Brooklyn sub repos. However, I do have an issue when building this one: https://github.com/apache/brooklyn-server. Some of the tests within that repo fail to create folders/files, even though the docker container is ran with the
uid
andgid
of the folder owner (based on these instructions: https://github.com/carlossg/docker-maven#running-as-non-root)To reproduce:
git clone https://github.com/apache/brooklyn-server
cd brooklyn-server
docker build -t brooklyn:server .
docker run --rm -i --name brooklyn-server -u $(id -u ${whoami}):$(id -g ${whoami}) -v ${HOME}/.m2:/var/maven/.m2 -v ${PWD}:/usr/build -w /usr/build -e MAVEN_CONFIG=/var/maven/.m2 brooklyn:server mvn clean install -Duser.home=/var/maven
This will fail with multiple
An
ls -la
on the host machine and within thebrooklyn-server
folder shows that the owner is the user I run the docker container with:What is very strange is that other subrepos like https://github.com/apache/brooklyn-library works perfectly fine with the same config. In any case, the code is actually compiled properly in each
target
folder . It seems that there is an issue when the file/folder to be created is at the root of the build folder.It definitely looks similar to #83.
The text was updated successfully, but these errors were encountered: