Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Unable to process bamboo specs in bamboo server - permission error


I am trying to scan bamboo Java specs residing in my linked repository(remote) via a manual scan from the bamboo server. But the scan errors out with the following error (Please note that I have disabled the bamboo security feature to process bamboo specs in docker):

[ERROR] Could not create local repository at /sbin/.m2/repository -> [Help 1]
org.apache.maven.repository.LocalRepositoryNotAccessibleException: Could not create local repository at /sbin/.m2/repository

Below is the complete error log:

Content of pom.xml used:
<?xml version="1.0" encoding="UTF-8" standalone="no"?><project xmlns="" xmlns:xsi="" xsi:schemaLocation="">
    <!--Edit template at BAMBOO_INSTALL/atlassian-bamboo/WEB-INF/classes/bamboo-specs-pom.xml-->


    <!-- Test dependencies -->
[INFO] Error stacktraces are turned on.
[ERROR] Could not create local repository at /sbin/.m2/repository -> [Help 1]
org.apache.maven.repository.LocalRepositoryNotAccessibleException: Could not create local repository at /sbin/.m2/repository
	at org.apache.maven.DefaultMaven.validateLocalRepository(
	at org.apache.maven.DefaultMaven.doExecute(
	at org.apache.maven.DefaultMaven.execute(
	at org.apache.maven.cli.MavenCli.execute(
	at org.apache.maven.cli.MavenCli.doMain(
	at org.apache.maven.cli.MavenCli.main(
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(
	at java.lang.reflect.Method.invoke(
	at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(
	at org.codehaus.plexus.classworlds.launcher.Launcher.launch(
	at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(
	at org.codehaus.plexus.classworlds.launcher.Launcher.main(
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1]
Unable to scan repository sre-bamboo-specs-v1 (15532045) for Bamboo Specs
com.atlassian.bamboo.repository.RepositoryException: Unable to scan repository sre-bamboo-specs-v1 (15532045) for Bamboo Specs
	at com.atlassian.bamboo.configuration.external.RepositoryStoredSpecsServiceImpl.lambda$runSpecsWithMaven$9(
	at java.util.concurrent.ThreadPoolExecutor.runWorker(
	at java.util.concurrent.ThreadPoolExecutor$
	at com.atlassian.bamboo.utils.BambooRunnables$
Caused by: com.atlassian.utils.process.ProcessException: Non-zero exit code: 1
	at com.atlassian.utils.process.PluggableProcessHandler.complete(
	at com.atlassian.utils.process.ExternalProcessImpl.wrapUpProcess(
	at com.atlassian.utils.process.ExternalProcessImpl.finish(
	at com.atlassian.utils.process.ExternalProcessImpl.execute(
	at com.atlassian.bamboo.configuration.external.RepositoryStoredSpecsServiceImpl.lambda$runSpecsWithMaven$9(
	... 8 more

Do you need help? Please visit the page.

Any help is highly appreciated

@Alexey Chystoprudov , Kindly help in getting a resolution to this problem.



1 answer

0 votes
Foong Atlassian Team Jan 18, 2019

Is Bamboo started with root user or sudo? Try starting Bamboo without root user or sudo.

May need to fix the file permission first with chown.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events