fix(dockerfiles): clean up dangling sockets on startup (#10468) #10481
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.
FTI-4525
(cherry picked from commit a6fe370)
Summary
This change adds a clean-up step to remove all sockets that a previous Kong run may have left in
$PREFIX
directory.Checklist
Full changelog
Dangling unix sockets have been a pain point in recent Kong versions and was dealt in traditional Kong in #9254, but the kong script is not called when starting Kong inside a container, so a similar change to
dockerfiles/entrypoint.sh
was added here.Issue reference
FTI-4525