93 lines
3.1 KiB
Markdown
93 lines
3.1 KiB
Markdown
# VM setup - Start docker container
|
|
|
|
|
|
## The `docker run` command
|
|
Once everything has been setup and configured, a docker container can be started with the following
|
|
command:
|
|
|
|
```
|
|
sudo docker run \
|
|
-d \
|
|
--dns 127.0.0.1 \
|
|
--name <instance-name> \
|
|
-p 80:80 \
|
|
-p 443:443 \
|
|
--restart unless-stopped \
|
|
[-v <host-cert-dir>:/etc/ssl/localcerts:ro] \
|
|
-v <host-secrets-dir>:/aio-secrets:ro \
|
|
-v <host-builds-dir>:/var/www/aio-builds \
|
|
[-v <host-logs-dir>:/var/log/aio] \
|
|
<name>[:<tag>]
|
|
```
|
|
|
|
Below is the same command with inline comments explaining each option. The aPI docs for `docker run`
|
|
can be found [here](https://docs.docker.com/engine/reference/run/).
|
|
|
|
```
|
|
sudo docker run \
|
|
|
|
# Start as a daemon.
|
|
-d \
|
|
|
|
# Use the local DNS server.
|
|
# (This is necessary for mapping internal URLs, e.g. for the Node.js upload-server.)
|
|
--dns 127.0.0.1 \
|
|
|
|
# USe `<instance-name>` as an alias for the container.
|
|
# Useful for running `docker` commands, e.g.: `docker stop <instance-name>`
|
|
--name <instance-name> \
|
|
|
|
# Map ports of the hosr VM (left) to ports of the docker container (right)
|
|
-p 80:80 \
|
|
-p 443:443 \
|
|
|
|
# Automatically restart the container (unless it was explicitly stopped by the user).
|
|
# (This ensures that the container will be automatically started on boot.)
|
|
--restart unless-stopped \
|
|
|
|
# The directory the contains the SSL certificates.
|
|
# (See [here](vm-setup--create-host-dirs-and-files.md) for more info.)
|
|
# If not provided, the container will use self-signed certificates.
|
|
[-v <host-cert-dir>:/etc/ssl/localcerts:ro] \
|
|
|
|
# The directory the contains the secrets (e.g. GitHub token, JWT secret, etc).
|
|
# (See [here](vm-setup--set-up-secrets.md) for more info.)
|
|
-v <host-secrets-dir>:/aio-secrets:ro \
|
|
|
|
# The uploaded build artifacts will stored to and served from this directory.
|
|
# (If you are using a persistent disk - as described [here](vm-setup--attach-persistent-disk.md) -
|
|
# this will be a directory inside the disk.)
|
|
-v <host-builds-dir>:/var/www/aio-builds \
|
|
|
|
# The directory where the logs are being kept.
|
|
# (See [here](vm-setup--create-host-dirs-and-files.md) for more info.)
|
|
# If not provided, the logs will be kept inside the container, which means they will be lost
|
|
# whenever a new container is created.
|
|
[-v <host-logs-dir>:/var/log/aio] \
|
|
|
|
# The name of the docker image to use (and an optional tag; defaults to `latest`).
|
|
# (See [here](vm-setup--create-docker-image.md) for instructions on how to create the iamge.)
|
|
<name>[:<tag>]
|
|
```
|
|
|
|
|
|
## Example
|
|
The following command would start a docker container based on the previously created `foobar-builds`
|
|
docker image, alias it as 'foobar-builds-1' and map predefined directories on the host VM to be used
|
|
by the container for accesing secrets and SSL certificates and keeping the build artifacts and logs.
|
|
|
|
```
|
|
sudo docker run \
|
|
-d \
|
|
--dns 127.0.0.1 \
|
|
--name foobar-builds-1 \
|
|
-p 80:80 \
|
|
-p 443:443 \
|
|
--restart unless-stopped \
|
|
-v /etc/ssl/localcerts:/etc/ssl/localcerts:ro \
|
|
-v /foobar-secrets:/aio-secrets:ro \
|
|
-v /mnt/disks/foobar-builds:/var/www/aio-builds \
|
|
-v /foobar-logs:/var/log/aio \
|
|
foobar-builds
|
|
```
|