I tried using chmod 777 <filename>, but it is going to be a long list. Yes, my docker commands were run with sudo, I'll try to make docker run without sudo.
Thanks, Nayeem. On Sat, Mar 28, 2020 at 11:57 PM Bandaru, Vivek Shresta <[email protected]> wrote: > Looks like you executed the docker compose command with root permissions, > i.e using sudo. (sudo docker-compose up -d) > If yes, I would suggest you clean your workspace or create a new workspace > altogether and execute the same command without sudo. > > A very bad hack would be to change the permissions of the files and > folders for which you’re encountering the issue by using the ‘chmod 777 > <filename>’ command, but you would have to change the permissions of all > the files and folders that were generated with the above mentioned command. > > Regards, > Vivek. > > > > *From: *Nayeemullah Baig <[email protected]> > *Reply-To: *"[email protected]" <[email protected]> > *Date: *Saturday, March 28, 2020 at 11:07 PM > *To: *"[email protected]" <[email protected]> > *Subject: *[External] Re: mvn install ends in error > > > > This message was sent from a non-IU address. Please exercise caution when > clicking links or opening attachments from external sources. > > > > Update: It was a maven issue. I modified the JAVA_HOME to use the > default-java. > > > > But now I'm getting a new error: [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-resources-plugin:2.5:resources > (default-resources) on project ide-integration: > /home/kubeadmin/gsoc/airavata/modules/ide-integration/src/main/resources/database_data/ca-key.pem > (Permission denied) -> [Help 1] > > > > Do I have to run the command with sudo? Or do I need to modify the > permissions of the .pem files? > > > > Thanks, > > Nayeemullah Baig > > > > On Sat, Mar 28, 2020 at 10:05 PM Nayeemullah Baig < > [email protected]> wrote: > > Hi, > > > > I'm setting up my local dev environment, currently I'm in the 'Start the > airavata server' phase and I get the following error when running the > command *mvn clean install -DskipTests* > > > > [INFO] Airavata Tools ..................................... SKIPPED > [INFO] Airavata Load Testing Client ....................... SKIPPED > [INFO] ide-integration .................................... SKIPPED > [INFO] > ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] > ------------------------------------------------------------------------ > [INFO] Total time: 5.414 s > [INFO] Finished at: 2020-03-28T21:58:17-04:00 > [INFO] > ------------------------------------------------------------------------ > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-compiler-plugin:3.6.1:compile > (default-compile) on project airavata-base-api: Compilation failure > [ERROR] javac: invalid target release: 11 > [ERROR] Usage: javac <options> <source files> > [ERROR] use -help for a list of possible options > [ERROR] > [ERROR] > [ERROR] -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the > -e switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, > please read the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException > [ERROR] > [ERROR] After correcting the problems, you can resume the build with the > command > [ERROR] mvn <args> -rf :airavata-base-api > > > > I thought it was an error because of Maven. So I reinstalled maven and > tried running it again. But I'm still getting the error. Any help would be > appreciated. > > > > Thanks, > > Nayeemullah Baig > >
