bamboo-docker | Bamboo Docker Rancher | Continuous Deployment library
kandi X-RAY | bamboo-docker Summary
kandi X-RAY | bamboo-docker Summary
Bamboo Docker Rancher
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of bamboo-docker
bamboo-docker Key Features
bamboo-docker Examples and Code Snippets
$ mkdir bamboo-stack
$ cd bamboo-stack
$ wget https://raw.githubusercontent.com/matisku/bamboo-docker/master/docker-compose.yml
$ docker-compose up -d .
Community Discussions
Trending Discussions on bamboo-docker
QUESTION
When I try to run a build with bamboo I get the following error:
...ANSWER
Answered 2021-Nov-05 at 11:44I was able to configure the Global Expiry to delete builds older than 90 days using the instructions at https://confluence.atlassian.com/bamboo/configuring-global-expiry-289277253.html :
- Click the icon in the Bamboo header and choose Overview.
- Click Expiry (under 'Plans') in the left-hand navigation panel.
From there the rest was pretty intuitive.
QUESTION
I am currently despairing at the attempt of setting up a docker build step in Atlassian Bamboo.
For starters, I just want to create a build configuration that runs the hello-world image as a proof of confluence. So far, I have failed.
I have tried following the steps on https://confluence.atlassian.com/bamboo0609/using-bamboo/jobs-and-tasks/configuring-tasks/configuring-the-docker-task-in-bamboo , but to no avail.
My setup is this:
We have Bamboo installed on an Ubuntu server. I also installed Docker on that server and added the bamboo
user to the docker
usergroup and restarted the server to make sure the permission change takes effect. At this point, docker run hello-world
works when I run it directly on the server. I can also confirm that this is the server that Bamboo runs on since Bamboo went offline whenever I restarted the server that I installed Docker on.
Then, I have added the docker capability to the server (the agent is the default agent, so it inherits this capability from the server). As the docker path, I have tried various things, none of which worked (aka, the following errors remained the same for each of these):
/snap/docker
(the first folder that I found on a manual search)/usr/bin/docker
(the recommended path, though on inspecting the Ubuntu server I quickly found out that nodocker
folder exists under/usr/bin
on the Ubuntu derver)/var/snap/docker/common/var-lib-docker
(the path that Docker returns as its Root Directory when I rundocker info
on the Ubuntu server)/var/snap/docker
(for good measure)
Now, for the runner, I have tried two different approaches.
First, I tried using a Docker runner with the following settings: Command: Run a Docker container Docker image: hello-world
This returns the following error message:
...ANSWER
Answered 2020-Jan-23 at 14:57Okay, I found out what caused this strange behaviour.
The problem was that I installed Docker using sudo snap install docker
, and apparently installing docker via snap causes problems with Bamboo.
So I got it to work using these simple steps:
- [Server] Uninstalled Snap Docker using
sudo snap remove docker
- [Server] Reinstalled Docker using
sudo apt install docker.io
- [Bamboo] Changed the path to Docker in the Server Capabilities to
/usr/bin/docker
After that, the hello-world image build succeeded and printed the expected output to the log.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install bamboo-docker
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page