Complete docker-compose.yml example? #5522

nemanjam · 2022-12-10T14:52:48Z

nemanjam
Dec 10, 2022

I can't find any tutorial with docker-compose.yml anywhere, do you know any? There is literally nothing on Google and YouTube.

Article in docs is very short and incomplete, e.g. one of the things that annoys me is that it says to enter the container and generate ssh keys, which makes no sense because they will disappear as soon as I restart the container.

Or just generate keys and add them via dokku ssh-keys:add? This is completely vague and undocumented.

cat ~/.ssh/authorized_keys | dokku ssh-keys:add admin

https://dokku.com/docs/getting-started/install/docker/

Do you know any tutorial or example how to setup Dokku with docker-compose.yml from start to finish?

Answered by josegonzalez

Dec 15, 2022

I ran the following modified command based on the docker install docs in conjunction with dokku/docker-run-export to generate a compose file. The only changes I made were:

change the binary to docker-run-export
remove container as part of the subcommand
add the --dre-project dokku flag

docker-run-export run --dre-project dokku \
  --env DOKKU_HOSTNAME=dokku.me \
  --env DOKKU_HOST_ROOT=/var/lib/dokku/home/dokku \
  --name dokku \
  --publish 3022:22 \
  --publish 8080:80 \
  --publish 8443:443 \
  --volume /var/lib/dokku:/mnt/dokku \
  --volume /var/run/docker.sock:/var/run/docker.sock \
  dokku/dokku:0.29.0

This is what it spit out:

---
name: dokku
services:
  app:
    container_name: d…

View full answer

cburkins · 2022-12-15T20:12:56Z

cburkins
Dec 15, 2022

Currently exploring same issue. I'm converting from Centos over to RHEL, so need to use the docker installation method. And yes, with the provided example for "docker container run", the home directory for dokku (/home/dokku) is not persistent, so upon container restart, you'll lose your ssh keys for the dokku user

3 replies

nemanjam Dec 15, 2022
Author

Here is what I have so far:

https://github.com/nemanjam/traefik-proxy/tree/main/apps/dokku

josegonzalez Dec 15, 2022
Maintainer

The data is indeed persistent, it isn't lost on reboot.

I ran the command with a change to where I mount things since I'm running it on a mac and not linux:

docker container run \
  --env DOKKU_HOSTNAME=dokku.me \
  --env DOKKU_HOST_ROOT=$PWD/tmp/home/dokku \
  --name dokku \
  --publish 3022:22 \
  --publish 8080:80 \
  --publish 8443:443 \
  --volume $PWD/tmp:/mnt/dokku \
  --volume /var/run/docker.sock:/var/run/docker.sock \
  dokku/dokku:0.29.0

Then with help from tree (brew install tree on a mac):

$ tree -d .

josediazgonzalez@Jose-Diaz-Gonzalez-3 tmp % tree -da .
.
└── tmp
    ├── etc
    │   ├── nginx
    │   └── ssh
    │       ├── ssh_config.d
    │       └── sshd_config.d
    ├── home
    │   └── dokku
    │       ├── .basher
    │       ├── .dokkurc
    │       └── .ssh
    └── var
        └── lib
            └── dokku
                ├── config
                │   ├── app-json
                │   ├── apps
                │   ├── builder
                │   ├── builder-dockerfile
                │   ├── builder-herokuish
                │   ├── builder-lambda
                │   ├── builder-pack
                │   ├── buildpacks
                │   ├── caddy
                │   │   └── --global
                │   ├── checks
                │   ├── common
                │   ├── git
                │   ├── logs
                │   ├── network
                │   ├── nginx
                │   │   └── --global
                │   ├── ps
                │   ├── registry
                │   ├── resource
                │   ├── scheduler
                │   ├── scheduler-docker-local
                │   └── traefik
                │       └── --global
                └── data
                    ├── app-json
                    ├── builder-lambda
                    ├── caddy
                    ├── git
                    ├── logs
                    ├── nginx-vhosts
                    │   └── dokku-errors
                    ├── ps
                    ├── scheduler-docker-local
                    ├── storage
                    └── traefik

51 directories

Now let me add an ssh key:

# enter the container
$ docker exec -it dokku bash

# add my ssh key
$ echo "ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQDekFLbbYvPXSzS0DdDH7wUs9YdTU8W5LEEJtHWcvL7biq3VX/PaE3Urp1Kn1Cg7G24FHONg3G8Aharqc4UIreQe+zzNy29Sv44uNWQaN4KSlQb8kAQr8BSdRDMtlMKyreEl05udMlyo5pMMyJ8RiFflvV7DmdnMunhX0+EYencgAUnAn5H4HvLj1BIqpe8av/Ryr/AKnknd+ATzBYD1ALGxPbz9r6wwRZYCBHIbCb+RI/ieigGUeqyF/PlbsyJ0gX6G6bdMV77jGI9mf7r7lo/PNING/wJRZ6FRwI4pYkYDogyBHTQU+qcUyoyp8VxpKgmhVGHl6YisYPJN/0okbhjxFEJhnFxKJgDIaXlqmyVLeOmKYuicw40Nk87o/7jPA4vrr3YjzuXl3XhB9ge2ymNOy6tPtt2hrWK9U4a5pmLS60+MItFvTHDV5c/xwHGnx4KaB06EY7aA3NKARfqSjtmXtQXverVYy2K+DnlgRnom+r2NtJoJ7ODu/S995gdpNk= [email protected]" | dokku ssh-keys:add admin

SHA256:qBI7zUo/XX/EKOvEuCW/9qDES8Kc2CzcRBgOO2N2DcM

$ dokku ssh-keys:list

SHA256:qBI7zUo/XX/EKOvEuCW/9qDES8Kc2CzcRBgOO2N2DcM NAME="admin" SSHCOMMAND_ALLOWED_KEYS="no-agent-forwarding,no-user-rc,no-X11-forwarding,no-port-forwarding"

After this, I verified my ssh key was on disk outside of the container (so I ran this in another terminal in that same directory I spawned dokku:

$ ls -lah tmp/home/dokku/.ssh
total 8
drwxr-xr-x@  3 josediazgonzalez  staff    96B Dec  6 16:02 .
drwxr-xr-x@ 10 josediazgonzalez  staff   320B Dec 15 15:15 ..
-rwx------@  1 josediazgonzalez  staff   803B Dec 15 15:25 authorized_keys

$ cat tmp/home/dokku/.ssh/authorized_keys
command="FINGERPRINT=SHA256:qBI7zUo/XX/EKOvEuCW/9qDES8Kc2CzcRBgOO2N2DcM NAME=\"admin\" `cat /home/dokku/.sshcommand` $SSH_ORIGINAL_COMMAND",no-agent-forwarding,no-user-rc,no-X11-forwarding,no-port-forwarding ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQDekFLbbYvPXSzS0DdDH7wUs9YdTU8W5LEEJtHWcvL7biq3VX/PaE3Urp1Kn1Cg7G24FHONg3G8Aharqc4UIreQe+zzNy29Sv44uNWQaN4KSlQb8kAQr8BSdRDMtlMKyreEl05udMlyo5pMMyJ8RiFflvV7DmdnMunhX0+EYencgAUnAn5H4HvLj1BIqpe8av/Ryr/AKnknd+ATzBYD1ALGxPbz9r6wwRZYCBHIbCb+RI/ieigGUeqyF/PlbsyJ0gX6G6bdMV77jGI9mf7r7lo/PNING/wJRZ6FRwI4pYkYDogyBHTQU+qcUyoyp8VxpKgmhVGHl6YisYPJN/0okbhjxFEJhnFxKJgDIaXlqmyVLeOmKYuicw40Nk87o/7jPA4vrr3YjzuXl3XhB9ge2ymNOy6tPtt2hrWK9U4a5pmLS60+MItFvTHDV5c/xwHGnx4KaB06EY7aA3NKARfqSjtmXtQXverVYy2K+DnlgRnom+r2NtJoJ7ODu/S995gdpNk= [email protected]

I then stopped dokku and waited for it to terminate. I checked the files on disk and they were still the same. Next I started it again and checked if they were still in the repo:

# stop the dokku container, wait a bit
$ docker stop dokku

# check the files
$ ls -lah tmp/home/dokku/.ssh
$ cat tmp/home/dokku/.ssh/authorized_keys

# start dokku
$ docker start dokku

# enter the container
$ docker exec -it dokku bash

# verify the keys are there
$ dokku ssh-keys:list

SHA256:qBI7zUo/XX/EKOvEuCW/9qDES8Kc2CzcRBgOO2N2DcM NAME="admin" SSHCOMMAND_ALLOWED_KEYS="no-agent-forwarding,no-user-rc,no-X11-forwarding,no-port-forwarding"

Are ya'll... assuming the files are somewhere other than in the directories that are mounted?

cburkins Dec 15, 2022

Ah, @josegonzalez you're right !! I was just in the midst of testing, and tried to verify persistent "authorized_keys" file. Accidentally looked at root's home dir instead of dokku's home dir. Doh. Looked at /home/dokku/.ssh, and sure enough, "authorized_keys" was there. Guess you're keying off the DOKKU_HOST_ROOT env var. Cool.

josegonzalez · 2022-12-15T20:38:02Z

josegonzalez
Dec 15, 2022
Maintainer

I ran the following modified command based on the docker install docs in conjunction with dokku/docker-run-export to generate a compose file. The only changes I made were:

change the binary to docker-run-export
remove container as part of the subcommand
add the --dre-project dokku flag

docker-run-export run --dre-project dokku \
  --env DOKKU_HOSTNAME=dokku.me \
  --env DOKKU_HOST_ROOT=/var/lib/dokku/home/dokku \
  --name dokku \
  --publish 3022:22 \
  --publish 8080:80 \
  --publish 8443:443 \
  --volume /var/lib/dokku:/mnt/dokku \
  --volume /var/run/docker.sock:/var/run/docker.sock \
  dokku/dokku:0.29.0

This is what it spit out:

---
name: dokku
services:
  app:
    container_name: dokku
    environment:
      DOKKU_HOST_ROOT: /var/lib/dokku/home/dokku
      DOKKU_HOSTNAME: dokku.me
    image: dokku/dokku:0.29.0
    ports:
    - mode: ingress
      target: 22
      published: "3022"
      protocol: tcp
    - mode: ingress
      target: 80
      published: "8080"
      protocol: tcp
    - mode: ingress
      target: 443
      published: "8443"
      protocol: tcp
    volumes:
    - type: bind
      source: /var/lib/dokku
      target: /mnt/dokku
    - type: bind
      source: /var/run/docker.sock
      target: /var/run/docker.sock

I don't provide more instructions than the docker run command on purpose because everyone's setup is different. One person's docker compose setup is not the same as the next, and folks might want kubernetes or ecs or nomad or whatever setups next. The docker run command is more or less all you need on a Linux VM to run things, and if you're trying to use another tool, you may want to familiarize yourself with how that tool maps docker container run args to its file format.

2 replies

nemanjam Dec 15, 2022
Author

Ok, thank you. It doesn't have to be instruction, it can be an example. As I mentioned above, I have this, and it seems to work ok.

version: '3.8'

services:
  dokku:
    image: dokku/dokku:0.29.0
    container_name: dokku
    ports:
      - "3022:22"
      # - "8443:443"
      # - "8080:80"
    environment:
      - DOKKU_HOSTNAME=dokku.${DOMAIN}
      - DOKKU_HOST_ROOT=/var/lib/dokku/home/dokku
    volumes:
      - ./dokku-data:/mnt/dokku
      - /var/run/docker.sock:/var/run/docker.sock
      # - /var/lib/dokku:/mnt/dokku
    networks:
      - proxy
    labels:
      - 'traefik.enable=true'
      - 'traefik.docker.network=proxy'
      - 'traefik.http.routers.dokku-https.rule=Host(`dokku.${DOMAIN}`)'
      - 'traefik.http.routers.dokku-https.entrypoints=websecure'
      - 'traefik.http.routers.dokku-https.service=dokku-svc'
      - 'traefik.http.services.dokku-svc.loadbalancer.server.port=80'

networks:
  proxy:
    external: true

josegonzalez Dec 15, 2022
Maintainer

I think you prove at least one of my points: you'll notice your /mnt/dokku is mounted elsewhere, you're not using nginx and instead mounting everything through traefik so you don't expose the same ports :)

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Complete docker-compose.yml example? #5522

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 2 comments 5 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

Select a reply

Complete docker-compose.yml example? #5522

nemanjam Dec 10, 2022

Replies: 2 comments · 5 replies

cburkins Dec 15, 2022

nemanjam Dec 15, 2022 Author

josegonzalez Dec 15, 2022 Maintainer

cburkins Dec 15, 2022

josegonzalez Dec 15, 2022 Maintainer

nemanjam Dec 15, 2022 Author

josegonzalez Dec 15, 2022 Maintainer

nemanjam
Dec 10, 2022

Replies: 2 comments 5 replies

cburkins
Dec 15, 2022

nemanjam Dec 15, 2022
Author

josegonzalez Dec 15, 2022
Maintainer

josegonzalez
Dec 15, 2022
Maintainer

nemanjam Dec 15, 2022
Author

josegonzalez Dec 15, 2022
Maintainer