Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Setting env var SEQCLI_CONNECTION_SERVERURL doesn't seem to work #365

Closed
richard-stafflink opened this issue Oct 11, 2024 · 1 comment · Fixed by #366
Closed

Setting env var SEQCLI_CONNECTION_SERVERURL doesn't seem to work #365

richard-stafflink opened this issue Oct 11, 2024 · 1 comment · Fixed by #366

Comments

@richard-stafflink
Copy link

Documentation mentions being able to use env vars in the form SEQCLI_<setting path>, with the example: SEQCLI_CONNECTION_SERVERURL
But I wasn't able to get it working.

Steps to reproduce:

Create a docker compose file with the contents:

version: '3.7'

services:
  seq:
    container_name: local-seq
    image: datalust/seq:latest
    restart: unless-stopped
    ports:
      - 81:80
      - 5341:5341
    environment:
      ACCEPT_EULA: 'Y'
    networks:
      - my_default

networks:
  my_default:
    name: my_default

Start the Seq container:

docker compose up -d --quiet-pull

Use the SeqCLI image to connect to it (using --server):

docker run --rm --network=my_default datalust/seqcli:latest feed list --server=http://local-seq
# nugetfeed-1 nuget.org

Use the SeqCLI image to connect to it (using env var SEQCLI_CONNECTION_SERVERURL):

docker run --rm --network=my_default -e SEQCLI_CONNECTION_SERVERURL=http://local-seq datalust/seqcli:latest feed list
# The command failed: Connection refused (localhost:5341) Connection refused

Confirm that env var SEQCLI_CONNECTION_SERVERURL gets passed to the container:

docker run --rm -it --entrypoint bash -e SEQCLI_CONNECTION_SERVERURL=http://local-seq --network=my_default datalust/seqcli:latest
# echo $SEQCLI_CONNECTION_SERVERURL
## http://local-seq
@nblumhardt
Copy link
Member

Version 2024.3.922, which includes this fix, has been published now.

Thanks again for the report!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants