Prefer tideways published docker container over custom container #543
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.
Description
We at Tideways started publishing containers for our daemon and PHP extension last year to ensure easier integration in docker setups and to make it easy to keep versions updated
We make available an image supporting mac and Linux on x86 and ARM at: https://github.com/tideways/container-images/pkgs/container/daemon
This PR uses that image over the classic install way via apt. It's faster and will ensure up to do date versions easier and in a more docker supported way.
The effective changes of this PR are minimal, with a change in hostname and that the daemon will now listen to IPv6 as well as IPv4
Related resources
https://support.tideways.com/documentation/setup/installation/docker-with-compose.html#tideways-daemon-container
Checklist