fix: Pin docker systemd services to the same docker version #849
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 latest moby upstream changes expect a
containerd
service to be installed and run independently. Thus if you were to build the AMI in master right now (we do this to get the latest ami security updates) it would cause the buildkite-ami to fail to start the docker-service and hence the machine gets killed. This fix pins the systemd images to the docker version so that the AMI's will be correctly aligned with the expected docker start commands.Links