Database initialization is not working

[cpang2]

Tried to create database user and database in docker-compose.yml but it is not working. Nothing gets created. Please advise.

influxdb:
image: influxdb:latest
restart: always
container_name: influxdb
ports:
- "8086:8086"
environment:
- INFLUXDB_ADMIN_USER=USERNAME
- INFLUXDB_ADMIN_PASSWORD=PASS
- INFLUXDB_DB=DBTEST
- INFLUXDB_HTTP_ENABLED=true
- INFLUXDB_HTTP_AUTH_ENABLED=true

[dawidchyrzynski]

Any progress on this? I have the same issue when auth is enabled.

[dawidchyrzynski]

I've fixed the issue by escaping "true" value for INFLUXDB_HTTP_AUTH_ENABLED variable. My compose service looks like this now:

influxdb:
  image: influxdb:latest
  restart: always
  container_name: influxdb
  ports:
    - 8086:8086
  environment:
    INFLUXDB_DB: telemetry
    INFLUXDB_ADMIN_USER: influx_admin
    INFLUXDB_ADMIN_PASSWORD: pass
    INFLUXDB_HTTP_AUTH_ENABLED: "true"

@cpang2 can you confirm whether it works for you?

[repomaa]

Having the same issue. Passing true as a string does not fix it.

[IronSinew]

I am also seeing this issue

environment:
     - INFLUXDB_DB=database
     - INFLUXDB_ADMIN_USER=admin
     - INFLUXDB_ADMIN_PASSWORD=admin
     - INFLUXDB_HTTP_AUTH_ENABLED=true

Database is not initialized. Users are not created.

[mmodenesi]

Same issue, using docker-compose version 1.19.0, build 9e633ef

edit:

Sorry, my bad. Using image: "influxdb:latest" fixed it (I was using an old version before). So I can not reproduce this, but maybe you can confirm (after container is created) that your influxdb image (latest) is indeed a recent one.

[emriver]

As mentionned by @PSanetra in another thread, cleaning my influxdb volume fixed it for me (rm -rf /influxDbData)

[scho]

I ran into a similar issue. I've set INFLUXDB_DB, but no database was created.

There was an issue with the special characters not being properly escaped. In my case, the database was called metrics-live and the problem was the hyphen. I had to add quotes to the name, so that it worked ("metrics-live").

[halfbaked]

thanks to the comment above from @emriver . cleaning the volume fixed it for me.

[blockloop]

My problem was having influxd in my command:. The docker CMD executes a script which is a proxy to the influxd command, which executes all of the init stuff first.

OLD:

  influxdb:
    image: docker.io/influxdb:latest
    environment:
      - INFLUXDB_DB=prometheus
    volumes:
      - ./influxdb.conf:/etc/influxdb/influxdb.conf
    command:
      - 'influxd'
      - '-config'
      - '/etc/influxdb/influxdb.conf'

NEW:

  influxdb:
    image: docker.io/influxdb:latest
    environment:
      - INFLUXDB_DB=prometheus
    volumes:
      - ./influxdb.conf:/etc/influxdb/influxdb.conf
    command:
      - '-config'
      - '/etc/influxdb/influxdb.conf'

[lchachurski]

This is what worked for me using docker-compose. Keep in mind it doesn't work well when changing those settings back and forth. Once the database is initialized it will somehow rebel against changes and output weird errors while authenticating. In my case deleting /tmp/influxdb directory helped.

So delete any database dir first and then use the config below:

    influxdb:
        environment:
            INFLUXDB_DB: project_dev
            INFLUXDB_ADMIN_USER: admin
            INFLUXDB_ADMIN_PASSWORD: secret
            INFLUXDB_HTTP_AUTH_ENABLED: "true"
        image: influxdb:latest
        ports:
            - "8086:8086"
            - "8087:8082"
        volumes:
            - /tmp/influxdb:/var/lib/influxdb

[Surfict]

Hello, still have the problem with the current version.

[cooling75]

... Keep in mind it doesn't work well when changing those settings back and forth. Once the database is initialized it will somehow rebel against changes and output weird errors while authenticating. In my case deleting /tmp/influxdb directory helped.

Thank you for this hint, I struggled with this for hours. Deleting the volume and let docker-compose recreate it solved it.

[JoshEisele]

This issue is quite old - is there any hope that it will be fixed at all. Any workaround to set the ADMIN_USER, ADMIN_PASSWORD as well as the option to HTTP_AUTH_ENABLED at initial docker-compose?