Docker Deployment with Bamboo

[christok]

We are considering the possibility of implementing Docker in our CI pipeline. I'm new to the technology, but understand the basics. I have us to the point where Bamboo can pull a project from source, build the Docker image from the Dockerfile, and run and test that image as a container on the build server.

What is less clear to me is what to do with that image once it's ready for release. With our traditional IIS apps we simply push the build to each of our environments using msdeploy. However, there's not an obvious analogue for Bamboo deployments using Docker.

Any thoughts on best practices for doing this?

[christok]

Thanks for the response. What I'm looking for is the analogue to msdeploy and I think that's Docker Machine. Again, I'm new to Docker, so still trying to understand the ecosystem. 

A Docker Machine plugin could be pretty cool.

[Daniel Santos]

Hi @christok

We have a docker task in Bamboo that can simplify running docker containers or building docker images. This is the reference document about this task:

• Configuring the Docker task in Bamboo - Atlassian Documentation

I don't think we will have something out of the box specifically for the purpose you need, but if you can do it in terminal with some scripts and docker, you should be able to do in Bamboo using the same strategy.

I suggest you to run some tests with Bamboo, checking our docs and coming back with the blockers you face. It will be easier to help you moving forward.

[Daniel Santos]

Hi @christok

Thank you for sharing a good picture of where you are now.
You should be able to reproduce a similar deployment scenario with Bamboo.

I'm not sure if I really understand the problem you are facing. Can you describe the set of steps Bamboo should do to deploy your image?

The general configuration would be:

1. Have a deployment project with the needed environments.
2. The deployment project will get the image as an artifact or a reference to the registry that the image was uploaded.
3. It will deploy it to each deployment environment.

In case you miss any specific task you can still use a scrip task and put the sequence of command to deploy your image as expected.

Does it make sense? What am I missing from your question?