You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I have local installation of Bamboo 6.9.1 in Windows 10 machine.
Docker 18.09.2 with Hyper-V containers (default option)
Settings:
-expose daemon on port 2375 without TLS
-local drive C: shared to container
Enable Repository Stored Specs - checked
Process Bamboo Specs in Docker -checked
Docker image(required) : 'atlassian/bamboo-specs-runner:6.9.1'.
When i'm trying to process build specs, I have error:
Processing Specs within Docker containerUnable to scan repository bamboo-specs gh (753665) for Bamboo Specs com.atlassian.bamboo.repository.RepositoryException: Unable to scan repository bamboo-specs gh (753665) for Bamboo Specs at com.atlassian.bamboo.configuration.external.RepositoryStoredSpecsServiceImpl.lambda$runSpecsWithDocker$9(RepositoryStoredSpecsServiceImpl.java:864) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at com.atlassian.bamboo.utils.BambooRunnables$1.run(BambooRunnables.java:48) at com.atlassian.bamboo.security.ImpersonationHelper.runWith(ImpersonationHelper.java:26) at com.atlassian.bamboo.security.ImpersonationHelper.runWithSystemAuthority(ImpersonationHelper.java:17) at com.atlassian.bamboo.security.ImpersonationHelper$1.run(ImpersonationHelper.java:41) at java.lang.Thread.run(Thread.java:748) Caused by: com.spotify.docker.client.exceptions.DockerRequestException: Request error: POST http://localhost:2375/containers/create?name=bamboo-specs-685e946f-716d-4b1d-a92e-35c3aa66aa42: 400, body: {"message":"the working directory '\\mnt\\input' is invalid, it needs to be an absolute path"}
Looks like directory path in wrong format, passed to docker process. But how I can control over this ?