This repository was archived by the owner on May 2, 2024. It is now read-only.
Update base haproxy image #4
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The primary motivation is that `dockercloud/haproxy:1.5.1` in legacy links mode does not reload. `/reload.sh`sends a `USR1` signal, but that just causes a `User reload is not supported in legacy link mode` log message.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The primary motivation is that
dockercloud/haproxy:1.5.1in legacy link mode does not reload./reload.shsends aUSR1signal, but that just causes aUser reload is not supported in legacy link modelog message.With
dockercloud/haproxy:1.6.1, haproxy picks up the new certificates for new domains as they are added, even when started withdocker run --link ....