-
Notifications
You must be signed in to change notification settings - Fork 1
GettingStarted
- Windows 7/8/10 (64-bit)
- or Mac OS/X
- or any Linux distribution
- about 20 GB free disk space
If you have 'native' Docker already up & running, you should be able to run the workshop. You can go directly to step 3 (Clone the Repository), but first figure out what the IP address is of your computer. Our 'magic' script will do that as well, but not all types of configuration have been checked.
When in doubt whether you're brave (or you don't want to install Docker) better go the safe way and run it in the Docker Toolbox instead of native.
Sorry, better do some Pair Programming with your 64bit neighbour.
You can try a manual install of the components making up the Docker Toolbox: Oracle VirtualBox, Boot2Docker, Docker Machine, etc. This is not tested, and you probably will be busy for an hour to get it running.
- Visit https://www.docker.com/docker-toolbox
- Download and run the installer for your operating system
- You can unselect the following components, as we're not using them:
- Docker Compose
- Kitematic
- Git (if you already have a working Git client)
We'll arrange that most of the Docker storage lands on a different drive where you do have enough free space. Skip this section if you have plenty (about 20 GB) free space on your C drive.
- Using Windows explorer, create a folder on a disk with more than 20GB free space (e.g.
D:\docker-machines
) - Move the folder
C:\Users\<username>\.docker\machine
to your created directory. - Open a Command prompt with administrator rights
-
Windows **Start** menu, type `cmd`, right-click `cmd.exe`, click *"run as administrator"*
-
- Create a symbolic link on the original location and point it to the location where your data is stored by pasting the following command:
mklink /D c:\Users\<username>\.docker\machine d:\docker-machines\machine
You'll find this icon on your desktop to start the Docker QuickStart Terminal
- A virtual machine called
default
machine has started, but that one's not gonna cut it for this workshop. Stop it to save precious system resources by typing the following command:
docker-machine stop default
- Instead of the dinky
default
machine we'll create one with 4 CPU cores instead of one, 8 GB RAM instead of one, and connected to our private Docker Registry:
docker-machine create fordintysa-ci --driver virtualbox --virtualbox-cpu-count "2" --virtualbox-memory "4096"
- Now you can login to the newly created VM with ssh (Secure Shell) as follows:
docker-machine ssh fordintysa-ci
- Clone this repository and checkout branch
infra
with the following command:
git clone https://github.com/ordina-jtech/fordintysa-ci.git -b infra
- Within the virual machine the storage of the user's home directory is volatile. So when the virtual machine reboots, everything stored there is lost. So it's better to move the repo to a persistent location:
sudo mv fordintysa-ci /mnt/sda1/
Ofcourse Linux users can skip this step (or move the repo to a location of their own choice)
- Now we have to make this new location our current directory:
cd /mnt/sda1/fordintysa-ci
- Now you can execute the magic script:
./open.sh
Magic spells often don't work the first time you try, but I'm sure you'll figure it out!
What to do next will be explained by the script once it has started.