Mymac:~ demokritos$ sudo mkdir -p /opt/teamcity_server/logs You can see `stat $folder` to display the permissions. We need to create folders, give permission to our group, and share folder with docker. Mymac:~ demokritos$ eval $(docker-machine env teamcityserver) # Run this command to configure your shell: # eval $(docker-machine env teamcityserver) Mymac:~ demokritos$ docker-machine env teamcityserverĮxport DOCKER_HOST="tcp://192.168.99.100:2376"Įxport DOCKER_CERT_PATH="/Users/demokritos/.docker/machine/machines/teamcityserver" export DOCKER_MACHINE_NAME="teamcityserver" You may need to re-run the `docker-machine env` command. Started machines may have new IP addresses. Mymac:~ demokritos$ docker-machine start teamcityserver Mymac:~ demokritos$ docker-machine create -driver virtualbox teamcityserver Why not Docker-for-Mac, purely I want to rely on VirtualBox to manage my machines, and keep environment variables for Virtualbox VMs. There will be 2 folders required on my host for TeamCity server: data folder, and logs folder to be introduced as volumes to the server container. I will use docker’s Mac Toolbox to create TeamCity server and agents. There are quite things I will cover to have a good touch on containers. After I saw JetBrains has the official docker image at DockerHub, I decided to do it sooner, than later. Because I am doing quite a number of trainings, demos, talks about Continuous Delivery, having the CI server/agents portable and containerised is a big win for me. One of the sessions at JaxLondon, Paul Stack mentioned they were running TeamCity on containers at HashiCorp.
0 Comments
Leave a Reply. |