[HELP] Stacks location and volume mapping

[holocronology]

Okay, maybe I'm being dense, but I don't understand what you are trying to say here:

      # ⚠️⚠️ If you did it wrong, your data could end up be written into a wrong path.
      # ✔️✔️✔️✔️ CORRECT: - /my-stacks:/my-stacks (Both paths match)
      # ❌❌❌❌ WRONG: - /docker:/my-stacks (Both paths do not match)
      - /opt/stacks:/opt/stacks
    environment:
      # Tell Dockge where is your stacks directory
      - DOCKGE_STACKS_DIR=/opt/stacks

Where exactly do I put the volume pathing on my host server?

Is this not accurate and why?

[louislam]

It is not easy to explain. I find that some people are also confused, I don't know how to make it clear.

I show you more examples here, hope you find the pattern.

CORRECT Examples:

• /volume1/docker/dockge-stacks:/volume1/docker/dockge-stacks
• /a:/a
• /stacks:/stacks
• /my-stacks:/my-stacks
• /opt/stacks:/opt/stacks

INCORRECT Examples:

• /a:/b
• /docker:/opt/stacks
• /volume1/docker/dockge-stacks:/my-stacks
• /stacks:/opt/stacks

Container's Path === Host's Path === MUST

It is a relative path issue of docker-compose which tries to do docker-compose up in the container but the docker server is actually in the host.

This stackoverall post explains more in details:
https://stackoverflow.com/questions/63802193/docker-compose-remote-context-path-relative-to-local-machine-instead-of-remote

[ToshY]

@louislam I'm not sure why your "INCORRECT Examples" denote that the host directory cannot be different from the container directory.

I have the following directory structure:

/var/tools/collection/
├── dockge/
│   └── .env
│   └── compose.yaml
└── kuma/
    └── compose.yaml

And use the following compose.yaml for dockge.

/var/tools/collection/dockge/compose.yaml

version: '3.9'

x-restart: &restart-always
  restart: always

services:
  dockge:
    image: louislam/dockge:${DOCKGE_IMAGE_VERSION}
    <<: [*restart-always]
    security_opt:
      - no-new-privileges:true
    environment:
      DOCKGE_STACKS_DIR: ${DOCKGE_STACKS_DIR_CONTAINER:-/opt/stacks}
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - dockge:/app/data
      - ${DOCKGE_STACKS_DIR_HOST:-/opt/stacks}:${DOCKGE_STACKS_DIR_CONTAINER:-/opt/stacks}
    networks:
      - dockge
      - proxy

volumes:
  dockge:
    driver: local

networks:
  dockge:
    driver: bridge
  proxy:
    external: true

Having the following .env variables defined for dockge.

/var/tools/collection/dockge/.env

DOCKGE_IMAGE_VERSION="1"
DOCKGE_STACKS_DIR_HOST="../" # resolves to "/var/tools/collection" on host
DOCKGE_STACKS_DIR_CONTAINER=

This works fine and mounts the stacks in /var/tools/collection from host to /opt/stacks in the container.

[RyanBalfanz]

+1

This is also discussed over at #146, where I suggested a start to change the example compose file with the confusing comments.

This reply by @ToshY makes sense to me. IMHO he documentation is just a bit lacking. Let's fix that for everyone else who might not find this or the other discussion thread.

[holocronology]

I also agree with @RyanBalfanz . The guide and comments are confusing. Especially since I had it working differently--but like @louislam said, it might work but with files in an unintended location. It is confusing, especially for someone with good knowledge, but not deep docker/compose/code knowledge (aka like me).

[louislam]

Also you can use docker compose ls to verify if the compose file in the correct.

In your case, the config path should start with /volume1/docker/dockge-stacks.

[holocronology]

Okay, so it need to be the same in all three locations?

It seems to be working the way I have it, but maybe something isn't and I'm not seeing it.

So I should have this:

[louislam]

Yes, you got it.

[holocronology]

So, I'm assuming that since I'm still seeing this in terminal, I need to nuke the entire Dockge container and settings and start over?

[louislam]

At this moment, you can docker-compose down all your stacks and start the stacks again in Dockge.

In future, I think Dockge should auto detect such problem and auto fix.

[mooglestiltzkin]

the closest match i use to yours louis was

/mnt/docker/dockge-stacks:/mnt/docker/dockge-stacks

i use jailmaker to bind the docker jail in the docker config for jailmaker e.g.

on truenas /mnt/tank/docker/data/dockge

so in docker config for jailmaker its bound as

/mnt/tank/docker/:/mnt/docker

then in compose you use /mnt/docker/data/dockge to put the dockge permanent configs.

others directories for my docker layout

/docker/data

/docker/stacks

/tank3

full pathing for /tank3 is /mnt/tank2/tank3 this is a separate dataset pool where media is stored. you also have to bind this in jailmaker docker config so you can then do /mnt/tank3 for your docker compose.

so dockge i did /docker/stacks/ this is where dockge puts the docker-compose yamls and .env files

    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - /mnt/docker/data/dockge/data:/app/data
        
      # If you want to use private registries, you need to share the auth file with Dockge:
      # - /root/.docker/:/root/.docker

      # Stacks Directory
      # ⚠️ READ IT CAREFULLY. If you did it wrong, your data could end up writing into a WRONG PATH.
      # ⚠️ 1. FULL path only. No relative path (MUST)
      # ⚠️ 2. Left Stacks Path === Right Stacks Path (MUST)
      - /mnt/docker/stacks:/mnt/docker/stacks
    environment:
      # Tell Dockge where is your stacks directory
      - DOCKGE_STACKS_DIR=/mnt/docker/stacks

this setup works for me on a truenas using jailmaker to create docker.

if not mistaken, i think what louis meant, was either that

1. /opt/stacks:/opt/stacks both sides matching exactly
2. /opt/stacks:/opt/stacks this part is the same but if you your entry for this would be say /mnt/docker/data/opt/stacks:/opt/stacks

wasn't sure which between these 2 he meant but i used the first example and copied both sides the same and just worked.
/mnt/docker/dockge-stacks:/mnt/docker/dockge-stacks

the pathing was already short to begin with for me, because i had shortened it by binding mount to jailmaker. for jailmaker for use in docker compose pathing we use the jailmaker binds, not your original full pathing for the truenas datasets.

hope this helps.