0

I saw couple of tutorials on continuous deployment (on docker.com, on codecentric.de, on devopscube.com).

Overall I saw two approaches:

  1. Set two types of jenkins server (master and slave). Master is in a docker container and slave on the host machine.

  2. Jenkins server in docker container. They set up the link to the host and using that link the jenkins can create or recreate docker images.

In the first approach - I do not understand why they set up additional jenkins server residing inside the docker container. Is not it enough just to have jenkins server on host machine alongside with docker container?

The second approach seems to me a bit insecure because process from container is accessing host OS. Does it have any benefits?

Thanks for any useful info.

StephenKing
  • 36,187
  • 11
  • 83
  • 112
mark
  • 354
  • 2
  • 5
  • 15
  • 1
    My idea/understanding of docker is to not mix containers with software on the host (except for tools like git for managing `docker-compose.yml` and other files). As for option 2: there is also Docker in Docker. And security depends on what you are using it for - just yourself, limited access or can everyone sign up and use your jenkins instance. – Martin Aug 08 '16 at 12:03
  • @mgansler I tried o have jenkins in docker and build other images using docker API from this jenkins container but somehow it was not able to execute the task (there are 2 executors free but it was not able to use them - the build was always in idle) – mark Aug 15 '16 at 08:31

0 Answers0