-
Notifications
You must be signed in to change notification settings - Fork 21
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
Binding to PIPELINE2_WS_HOST #717
Labels
Comments
Is this related to these issues?
I may have fixed this last year, in commit daisy/pipeline-framework@37cf09e. Can you check? |
Ah, yes, I thought I might have brought this up before. So this is a duplicate. I'll let you know on those issues when I've tried 👍 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We have a file ("
docker-entrypoint.sh
") which I have set up to be used as the entrypoint when running Pipeline 2 in our docker environment (docker swarm):Let's say
PIPELINE2_WS_HOST
isexample.com
. This setup will make it bind to and useexample.com
as0.0.0.0
internally, while still usingexample.com
in API responses where there are URLs to jobs, scripts etc.I'm not sure if this is a docker specific issue, or if it's a more general networking issue. But maybe there should be a separate environment variable for which host to bind to.
This couldmake docker setup easier, as was brought up in #709
The text was updated successfully, but these errors were encountered: