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

SSL example does not work. #180

Open
cmdctl opened this issue Nov 6, 2021 · 2 comments · May be fixed by #187
Open

SSL example does not work. #180

cmdctl opened this issue Nov 6, 2021 · 2 comments · May be fixed by #187

Comments

@cmdctl
Copy link

cmdctl commented Nov 6, 2021

The SSL example given in the docs does not work...
When ENABLE_SSL env variable is set then the container exits with code 127

Steps to reproduce:

  • Run the container with the example given in the SSL section of the README.md
docker run  --net=host \
           -e ENABLE_SSL=1 \
           lensesio/fast-data-dev

Actual:
The container exits immediately with code 127

Output docker ps -a

CONTAINER ID   IMAGE                    COMMAND                  CREATED          STATUS                        PORTS     NAMES
ed34dd08f518   lensesio/fast-data-dev   "/usr/bin/dumb-init …"   49 seconds ago   Exited (127) 49 seconds ago             unruffled_leavitt

Output docker logs ed34dd08f518

TLS enabled.
Creating CA and key-cert pairs.
@andsarr
Copy link

andsarr commented Dec 10, 2021

This is the problem:

/usr/local/bin/setup-and-run.sh: line 397: /usr/local/bin/quickcert: No such file or directory

Installing this one solves the issue: https://github.com/andmarios/quickcert/releases/download/1.1/quickcert-1.1-linux-amd64

The QUICKCERT_URL should be changed in the dockerfile

anamarija added a commit to true-north-engineering/fast-data-dev that referenced this issue Aug 26, 2022
@anamarija anamarija linked a pull request Aug 26, 2022 that will close this issue
@viveks7
Copy link

viveks7 commented Sep 16, 2023

@andmarios Can we merge this? Facing the same issue.

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.

3 participants