Docker compose is a popular way to define multi-container applications using a infrastructure as code approach.
If you personally prefer to use
docker compose, then here is a sample to get
version: "3.8" services: olivetin: container_name: olivetin image: jamesread/olivetin volumes: - /docker/olivetin:/config # replace host path or volume as needed ports: - "1337:1337" restart: unless-stopped networks: web: # should match the network defined under the container's networks section external: true
You should be able to browse to http://yourserver:1337 (or similar) to get to the web interface.
If you see the OliveTin page popup in your browser, you can jump to the configuration section as the next step.
If you want to use OliveTin running in a container to control other Docker containers, you will need to pass through the Docker sock in your compose file.
You will need to adjust your docker-compose file to include the docker socket, like this;
`docker-compose.yml` including docker socket
version: "3.8" services: olivetin: container_name: olivetin image: jamesread/olivetin volumes: - /docker/olivetin:/config # replace host path or volume as needed - /var/run/docker.sock:/var/run/docker.sock ...
You will probably need to tell this container to run as root as well, to control docker (see below).
This is the correct way to tell the OliveTin container to run as root (or any other user);
version: "3.8" services: olivetin: container_name: olivetin image: jamesread/olivetin user: root ...
|PUID and PGID are not used by the official OliveTin container image.|
Traefik is a popular reverse proxy that seems to be used a lot in people’s Docker compose setups.
docker-compose.yml example above to include the following labels;
... labels: - traefik.http.routers.olivetin.rule=Host(`run.your.domain`) - traefik.http.routers.olivetin.tls.certresolver=lets-encrypt ...