Docker Secret Support

[beny2000]

Hi, love the project. It's the most straightforward approach to monitoring I've come across. I was wondering if there is (or will be) Docker secret support for environment variables. I'd like to be able to specify the agent key in a Docker secret and pass the file path as the environment variable, as is common with other services.

For example, being able to do something like this would be great

beszel-agent:
  image: henrygd/beszel-agent
  network_mode: host
  volumes:
    - /var/run/docker.sock:/var/run/docker.sock:ro
  environment:
    PORT: 45879
    KEY_FILE: /run/secrets/beszel_agent_key
  secrets:
     - beszel_agent_key

Thanks

[beny2000]

Added support for this in #412

[henrygd]

Thanks, I'll check it out tomorrow.

[arunoruto]

The KEY_FILE support will make it easier to support a nix service module in the future!

[jo-chemla]

Would be great to have this feature added to the docs, as well as inform on how to use it without docker-secrets.

I tried multiple variations (via portainer) of the following, before realizing the PR was merged after the latest release of jan 6. Then I tried using a beta container-image image: ghcr.io/henrygd/beszel-agent, but it seems that these are not public, which is probably intentional: Failed to deploy a stack: compose up operation failed: Error response from daemon: Head "https://ghcr.io/v2/henrygd/beszel-agent/manifests/latest": denied.

    volumes:
      - /var/run/docker.sock:/var/run/docker.sock:ro
      - /host-path/beszel/beszel-key-file.txt:/beszel/beszel-key-file.txt
    environment:
      # KEY: "ssh-ed123456 random" 
      # KEY_FILE: /host-path/beszel/beszel-key-file.txt
      KEY_FILE: /beszel/beszel-key-file.txt 

EDIT:
I tried multiple other things, but beszel-agent lacks several commands like export, echo etc, so I could not edit container entrypoint or post_start commands.

    entrypoint: export KEY="ssh-ed12345 random" && /agent
    post_start:
      - command: echo "test" && KEY=$(cat /beszel/beszel-key-file.txt) && echo "$KEY" && echo "end"

Portainer does not accept within stack an env_file variable described by a relative-path, it has to be an absolute path from a volume that has been mounted to the portainer container itself. So I finally succeeded in defining KEY via environment file, by exposing the directory where the .env is located to portainer container, and assigning that as an env_file for the beszel-agent container.

[henrygd]

Sorry about that. The next release has been a bit delayed but I hope to have it wrapped up in the next few days.

[jo-chemla]

No worries and no need to rush, it's open-source!