If I input the token directly into the compose file everything works great, prometheus receives the metrics without issue. But if I try make use of docker secrets, I get the following: '+1000 Rack app ("GET /metrics" - (172.19.0.27)): #<ArgumentError: value must be a number'.
#GLOBAL#
PUID=1000
PGID=1000
UMASK=002
TZ=Australia/Melbourne
SECRETS_PATH=/appdata/ubuntu/docker/secrets
#CONTAINER_NAME
PLEX_EXP_CONTAINER_NAME=plex-exporter
#IMAGE_TAG
PLEX_EXP_IMAGE_TAG=latest
PLEX_SERVER_ADDRESS=http://<LAN IP OF PLEX MACHINE>:32400
#CONTAINER_PORTS
PLEX_EXP_HOST_PORT=9594
PLEX_EXP_CONT_PORT=9594
Any ideas here? As I said, the token itself works if I just use that (including copying out of the token file and pasting in compose), but throwing secrets into the mix is just not working. Not a fan of including api/token in docker-compose.yml or .env.
Sorry, there is no support for Docker secrets out of the box at the moment. It's unfortunately not common to support this, although I know the postgres container does support it natively.
Hello,
If I input the token directly into the compose file everything works great, prometheus receives the metrics without issue. But if I try make use of docker secrets, I get the following: '+1000 Rack app ("GET /metrics" - (172.19.0.27)): #<ArgumentError: value must be a number'.
I have tried the following:
All give the same error and promethesus lists the exporter as down.
Compose;
.env
Any ideas here? As I said, the token itself works if I just use that (including copying out of the token file and pasting in compose), but throwing secrets into the mix is just not working. Not a fan of including api/token in docker-compose.yml or .env.