Back to overview
Degraded

Build and runtime failures related to the OpenSSL 4 transition

Oct 6, 2026 at 3:08pm UTC
Affected services
Image builds & releases

Updated
Oct 6, 2026 at 10:21pm UTC

Additional information on troubleshooting and resolving issues with affected images is forthcoming. We will provide a link to the updated documentation when it goes live.

Some customers are seeing build or runtime failures related to the ongoing Chainguard OS transition to OpenSSL 4, mostly when adding packages to an image with apk add or copying binaries between images.

We continue to work through other reports related to the OpenSSL 4 transition.

If you are affected, please contact support with your image digest and the error output, including errors related to OpenSSL or cipher suites.

Updated
Oct 6, 2026 at 5:24pm UTC

Some customers are seeing build or runtime failures related to the ongoing Chainguard OS transition to OpenSSL 4, mostly when adding packages to an image with apk add or copying binaries between images.

We continue to work through other reports related to the OpenSSL 4 transition.

If you are affected, please contact support with your image digest and the error output, including errors related to OpenSSL or cipher suites.

Updated
Oct 6, 2026 at 4:27pm UTC

Some customers are seeing build or runtime failures related to the ongoing Chainguard OS transition to OpenSSL 4, mostly when adding packages to an image with apk add or copying binaries between images.

We continue to work through other reports related to the OpenSSL 4 transition.

If you are affected, please contact support with your image digest and the error output, including errors related to OpenSSL or cipher suites.

Created
Oct 6, 2026 at 3:08pm UTC

Some customers are seeing build or runtime failures related to the ongoing Chainguard OS transition to OpenSSL 4, mostly when adding packages to an image with apk add or copying binaries between images. Fixes are available or rolling out for the affected images, and building from a current image with current packages resolves most cases. If you are affected, please contact support with your image digest and the error output.