Skip to content

fix: Pin compatible Docker clients in Periphery images - #1614

Open
mvanhorn wants to merge 1 commit into
moghtech:mainfrom
mvanhorn:fix/1249-pin-periphery-docker-clients
Open

fix: Pin compatible Docker clients in Periphery images#1614
mvanhorn wants to merge 1 commit into
moghtech:mainfrom
mvanhorn:fix/1249-pin-periphery-docker-clients

Conversation

@mvanhorn

@mvanhorn mvanhorn commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

Constrain docker-ce-cli to the 28.x package line and docker-compose-plugin to the 5.0.x line in the shared Periphery dependency installer, while leaving the unrelated buildx package unchanged. Use apt's explicit version selection and downgrade support so all single-architecture, multi-architecture, and all-in-one Periphery Dockerfiles inherit the same compatible clients through their existing call to debian-deps.sh. Periphery container images currently install the newest docker-ce-cli and docker-compose-plugin packages from Docker's Debian repository. Docker CLI 29 and Compose 5.1 can fail against Docker Engine 27 when an IPv6 network gateway is returned with a CIDR suffix, causing stack restart, stop, destroy, deploy, and discovery operations to fail with ParseAddr(.../64).

Build the dependency layer from debian:trixie-slim using bin/periphery/debian-deps.sh; installation succeeds while a newer package version is present in the configured Docker repository; Query docker --version after installation and verify the bundled CLI remains on the 28.x compatibility line.

Closes #1249

@mvanhorn
mvanhorn force-pushed the fix/1249-pin-periphery-docker-clients branch from da70755 to d8a65f6 Compare September 3, 2026 17:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug] Actions on stacks sporadically fail (v2.0.0)

1 participant