Docker compose don't parse DATABASE_URL_FILE #1826

New Issue

2025-11-07T07:21:06-06:00

GiteaMirror commented

2025-11-07 07:21:06 -06:00

Originally created by @thejoelinux on GitHub (Jan 22, 2024).

Subject of the issue

We are trying to deploy the docker container in a Docker Swarm.
As the DATABASE_URL contains a password, we try to pass it via a DATABASE_URL_FILE env variable, but it is not parsed.
At the same time, when DATABASE_URL_FILE and DATABASE_URL are both defined, it throws an error.

Deployment environment

Docker swarm, vault-warden on MariaDB.

Steps to reproduce

Put the DATABASE_URL in a secret file (i.e. /run/secrets/database_url_secret), or a config...
Set DATABASE_URL_FILE=/run/secrets/database_url_secret

Expected behaviour

Vault connect to the database using the URL in the DATABASE_URL_FILE

Actual behaviour

The container don't start, complaining the database is not found.

Originally created by @thejoelinux on GitHub (Jan 22, 2024). ### Subject of the issue We are trying to deploy the docker container in a Docker Swarm. As the DATABASE_URL contains a password, we try to pass it via a DATABASE_URL_FILE env variable, but it is not parsed. At the same time, when DATABASE_URL_FILE and DATABASE_URL are both defined, it throws an error. ### Deployment environment Docker swarm, vault-warden on MariaDB. ### Steps to reproduce Put the DATABASE_URL in a secret file (i.e. /run/secrets/database_url_secret), or a config... Set DATABASE_URL_FILE=/run/secrets/database_url_secret ### Expected behaviour Vault connect to the database using the URL in the DATABASE_URL_FILE ### Actual behaviour The container don't start, complaining the database is not found.

GiteaMirror closed this issue

2025-11-07 07:21:07 -06:00

GiteaMirror commented

2025-11-07 07:21:09 -06:00

@BlackDex commented on GitHub (Jan 22, 2024):

Works just fine for me. Can you share your docker-compose.yml relevant parts?

This is what worked for me:

---
version: '3.8'

services:
  vaultwarden:
    image: ghcr.io/dani-garcia/vaultwarden:latest-alpine
    network_mode: host
    container_name: vaultwarden
    restart: unless-stopped
    environment:
      TZ: Europe/Amsterdam
      ROCKET_PORT: 8888
      DATABASE_URL_FILE: /run/secrets/database_url
      I_REALLY_WANT_VOLATILE_STORAGE: true
      EXTENDED_LOGGING: true
      LOG_LEVEL: info
      DISABLE_ADMIN_TOKEN: true
    secrets:
      - database_url

secrets:
  database_url:
    file: mariadb_url.txt

@BlackDex commented on GitHub (Jan 22, 2024): Works just fine for me. Can you share your docker-compose.yml relevant parts? This is what worked for me: ```yaml --- version: '3.8' services: vaultwarden: image: ghcr.io/dani-garcia/vaultwarden:latest-alpine network_mode: host container_name: vaultwarden restart: unless-stopped environment: TZ: Europe/Amsterdam ROCKET_PORT: 8888 DATABASE_URL_FILE: /run/secrets/database_url I_REALLY_WANT_VOLATILE_STORAGE: true EXTENDED_LOGGING: true LOG_LEVEL: info DISABLE_ADMIN_TOKEN: true secrets: - database_url secrets: database_url: file: mariadb_url.txt ```

GiteaMirror commented

2025-11-07 07:21:09 -06:00

@BlackDex commented on GitHub (Jan 22, 2024):

Also, the error message when you define both specifically states to not define both.

You should not define both DATABASE_URL and DATABASE_URL_FILE!

That is as intended, and the message seems to be clearly stating what the issue is and how to resolve it.

@BlackDex commented on GitHub (Jan 22, 2024): Also, the error message when you define both specifically states to not define both. ``` You should not define both DATABASE_URL and DATABASE_URL_FILE! ``` That is as intended, and the message seems to be clearly stating what the issue is and how to resolve it.