Are .env files supported?

[Dima-Kal]

Im using .env file for all my stacks, and all of them report missing vars:

WARN[0000] The "DOCKER_STORAGE_PATH" variable is not set. Defaulting to a blank string.
WARN[0000] The "DOCKER_NETWORK" variable is not set. Defaulting to a blank string.
WARN[0000] The "SERVER_DOMAIN" variable is not set. Defaulting to a blank string.
WARN[0000] The "SERVER_DOMAIN" variable is not set. Defaulting to a blank string.
WARN[0000] The "DOCKER_NETWORK" variable is not set. Defaulting to a blank string.

[ToshY]

I'm also using .env for my existing stacks in dockge without any console warnings when starting the stack. How does your compose.yaml for your stack look like then?

[Dima-Kal]

For example:

  authelia:
    image: authelia/authelia:v4.38.0-beta2
    container_name: authelia
    user: "1000"
    volumes:
      #- ./authelia:/config
      - "./configs/authelia/authelia-config.yml:/config/configuration.yml:ro"
      - "./configs/authelia/authelia-users-database.yml:/config/users_database.yml:ro"
      - "./configs/authelia/private.pem:/config/private.pem:ro"
      - "${DOCKER_STORAGE_PATH}/network/authelia/config:/config"
    networks:
      - ${DOCKER_NETWORK}
    labels:
      - "traefik.enable=true"
      - "traefik.http.routers.authelia.rule=Host(`authelia.${SERVER_DOMAIN}`, `auth.${SERVER_DOMAIN}`)"
     ```

[louislam]

Where did you put your .env file?

As long as you set the stacks path correctly, dockge's deploy/start are just like a normal "docker compose up".

Correct stacks path related discussion:
#26

[OJ7]

Does Dockge support editing .env files through the UI?

[trythatagain]

I assume this is adding a .env file in the same place as the compose.yml for whatever container you're creating? If this gets included, could this also be used to setup a 'global.env' file, say a separate button next to the 'Home' button?
Especially if a 0 byte 'global.env' file is created when spinning up Dockge and included in the 'docker compose -up' command.

[syko9000]

Yes, this is just the .env beside the .yml. I have no design decisions but I think that global.env would be its own "tab" in the settings pages. Not sure where the file would be stored (just in stacks maybe? so compose files would just ../global.env. Adding it to the docker compose up command doesn't seem that complicated either. I'm be happy to put that together, if @louislam wants it.

[almereyda]

What kind of data would you put in a global environment file? I'm unsure I understand how this could be used.

[trythatagain]

I use a global .env file as I use OMV, and OMV recommends using the full path for directories in compose files, I have used sym-links, but as I can use a global .env file I prefer the ,env file.
Especially useful when spinning up media containers.

for example -
APPDATA="/srv/dev-disk-by-uuid-2b9b3914-0f0d-4737-9638-f6740d0ddf18/appdata"
TZ="Europe/London"
PUID=1000
PGID=100

Then in my compose.yml
volumes:
- /var/run/docker.sock:/var/run/docker.sock
- $APPDATA/dockge:/app/data
environment:
- PUID=$PUID
- PGID=$PGID
- TZ=$TZ

[EdgarM73]

Hi,

my main reason for an global .env file:

I have several compose files and i am using a ip range for all of my containers.

there for i have this design:

...
networks:
dockervlan:
ipv4_address: ${IP_IOBROKER}
...

and the ip adresses for all of my containers are in one global .env file which is beeing sources for my linux user.

and my global .env looks like this:
...
IP_IOBROKER='172.23.2.1'
IP_DECONZ='172.23.2.2'
IP_GITEA='172.23.2.3'
IP_FS='172.23.2.4'
IP_GRAFANA='172.23.2.5'
IP_WARDEN='172.23.2.10'
IP_DIYHUE='172.23.2.197'
IP_PHPMYADMIN='172.23.2.6'
IP_SEAFILE='172.23.2.7'
IP_GLANCES='172.23.2.8'
IP_DOZZLE='172.23.2.9'
IP_PAPERLESS='172.23.2.20'
IP_WATCHTOWER='172.23.2.21'
IP_CODE='172.23.2.22'
IP_BOOKSTACK='172.23.2.23'
IP_PGADMIN='172.23.2.26'
...

It would be even better, if this could be done in dockge.

regards
E

[Dima-Kal]

Where did you put your .env file?

As long as you set the stacks path correctly, dockge's deploy/start are just like a normal "docker compose up".

Correct stacks path related discussion: #26

Heres an example for one of the stacks folder:

[louislam]

If you don't provide the full path to Dockge, Dockge don't know your actual path on your host.

Why Portainer don't need this? Because they kidnapped your compose files, you have no control of that.

[Dima-Kal]

I've tried to create the following addition to my script, to create an ENV variable for root path and pass it to the compose, but that didn't work:

rootDir=$( cd "$(dirname "${BASH_SOURCE[0]}")" ; pwd -P )
echo "Root dir is ${rootDir}"

sed -i "s|^DOCKER_STACK_PATH=.*|DOCKER_STACK_PATH=$rootDir|" $rootDir/.env

The env file is updated correctly:

DOCKER_STACK_PATH=/home/dimak/selfhost

  dockge:
    image: louislam/dockge:1
    restart: unless-stopped
    env_file: .env
    networks:
      - ${DOCKER_NETWORK}
    dns:
      - ${PIHOLE_DNS}
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - ${DOCKER_STORAGE_PATH}/dockge/data:/app/data

      - ${DOCKER_STACK_PATH}:${DOCKER_STACK_PATH}
    environment:
      # Tell Dockge where is your stacks directory
      - DOCKGE_STACKS_DIR=${DOCKER_STACK_PATH}
    labels:
      - "traefik.enable=true"
      - "traefik.http.routers.dockge.rule=Host(`dockge.${SERVER_DOMAIN}`)"
      - "traefik.http.services.dockge.loadbalancer.server.port=5001"

used this to bring up the stack:
docker compose --env-file .env up -d

but now dockge is broken, no working stacks, and if i echo:
docker exec -it selfhost-dockge-1 echo ${DOCKGE_STACKS_DIR}
it returns empty value

[Dima-Kal]

if i write it hardcoded it also doesn't work:

      - /home/dimak/selfhost:/home/dimak/selfhost
    environment:
      # Tell Dockge where is your stacks directory
      - DOCKGE_STACKS_DIR=/home/dimak/selfhost

[louislam]

Since your previous path is ./stacks, should it be /home/dimak/selfhost/stacks?

[Dima-Kal]

It doesnt do recursive folders scan?
yes changing it to stacks working

But i notice that it using a (relatively to portainerr) a lot of CPU ~4%, while portainer only using ~0.09% , is there a reason for such high usage?

[trythatagain]

I've done some work on this path thing, and I do think the docs are correct. I'll show my 'dockge.yml' and my 'dozzle2.yml' and '.env', I know the dozzle2 example is simple, but it works fine and shows the logs for my 25+ containers.

From within Dockge, the 'compose.yml' file is saved in my stacks folder, in the dir 'dozzle2', I also saved the '.env' file in my stacks dir/dozzle2. Clicked save and start and up comes dozzle2 with no errors and as I said, shows all my container logs.

`
######################## dockge

version: "3.8"
services:
dockge:
container_name: dockge
image: louislam/dockge:latest
ports:
# Host Port:Container Port
- 5001:5001
volumes:
- /var/run/docker.sock:/var/run/docker.sock
- $APPDATA/dockge:/app/data

  # If you want to use private registries, you need to share the auth file with Dockge:
  # - /root/.docker/:/root/.docker

  # Your stacks directory in the host (The paths inside container must be the same as the host)
  # ⚠️⚠️ If you did it wrong, your data could end up be written into a wrong path.
  # ✔️✔️✔️✔️ CORRECT EXAMPLE: - /my-stacks:/my-stacks (Both paths match)
  # ❌❌❌❌ WRONG EXAMPLE: - /docker:/my-stacks (Both paths do not match)

  #This how the paths are used in OMV, i.e the full path is recommended 
  - /srv/dev-disk-by-uuid-2b9b3914-0f0d-4737-9638-f6740d0dcc18/compose:/opt/stacks


environment:
  # Tell Dockge where is your stacks directory
  # Please note this equals the right hand value of my stacks volume 
  - DOCKGE_STACKS_DIR:/opt/stacks

networks:
    - mynet
restart: unless-stopped

networks:
mynet:
external: true
`

`
########################

dozzle2

########################

version: "2"
services:
dozzle2:
container_name: dozzle2
image: amir20/dozzle:latest
volumes:
#- /var/run/docker.sock:/var/run/docker.sock
# Please see .env for my environment variables
- $DOCKER:/var/run/docker.sock
ports:
- 19999:8080
networks:
#- mynet
# Again see my .env file
- $MYNET

restart: unless-stopped

networks:
mynet:
external: true
`

.env

MYNET="mynet" DOCKER="/var/run/docker.sock"

[mgrimace]

To add, it looks like if I use the .env for variables like image name (e.g., image: {IMAGE:?err}), ports, etc., that Dockge can’t read them (the compose still works, just the actual names, etc. don’t show up in the Dockge container view)

[louislam]

Just implemented this, but only basic syntax like ${PORT} or ${PORT:-8080}, because I cannot find a Node.js envsubst library that supports all syntax.

#268

[mgrimace]

Nice, I’ll check it out, thanks! Can Dockge update itself if it’s in the stack folder?

[louislam]

Unfortunately cannot, because during the update, Dockge will kill the update terminal in the middle of update process and Dcokge will kill itself too.

Or maybe I haven't found a solution yet.

[mgrimace]

That makes sense, thanks for all this work!