Skip to content

Conversation

@herzi
Copy link
Contributor

@herzi herzi commented Oct 29, 2025

Motivation

It looks like building images with containertool on Linux fails when using swift:slim as the base image (which is the default base image, I think.

Modifications

Update end to end and integration workflows to test both scratch and swift:slim base images.

Result

End-to-End Tests should now fail in release configuration.

Test Plan

Other tests are not affected by this.

@herzi
Copy link
Contributor Author

herzi commented Oct 29, 2025

For reference, I extracted the hummingbird + resource example where the expected failure can be observed in the GitHub Action logs.

@herzi herzi force-pushed the testing/release-configuration branch from 1a05631 to b3d7ac1 Compare October 30, 2025 07:11
@herzi herzi changed the title ci: Run End-to-End Tests for Debug and Release Configurations ci: Run End-to-End Tests forscratch and swift:slim Base Images Oct 30, 2025
@euanh euanh added the area/testing Improvements to tests. label Nov 3, 2025
@euanh euanh self-requested a review November 3, 2025 15:44
@euanh
Copy link
Collaborator

euanh commented Nov 3, 2025

Thanks for reporting this @herzi. I've reproduced this locally and I'm working on a fix. I've filed issue #166 to track it.

euanh added a commit that referenced this pull request Nov 21, 2025
…nux (#167)

Motivation
----------

In #164, @herzi reported a problem building container images based on
`swift:slim` on Linux. The root cause of the problem is that Docker Hub
now redirects pulls for `swift:slim` to an S3 bucked behind CloudFlare.
URLSession on macOS follows the redirect correctly, but URLSession on
Linux incorrectly includes an `Authorization` header which S3 rejects.

Modifications
-------------

Add a URLSession delegate which removes the `Authorization` header when
following a redirect.

Result
------

Pulling `swift:slim` from Docker Hub works again.

Fixes: #166 

Test Plan
---------

* #164 extended the end-to-end tests to use `swift:slim` as well as
`scratch`, demonstrating the problem. The extended tests now pass.
* All existing tests continue to pass.
@euanh euanh closed this Nov 21, 2025
@euanh euanh force-pushed the testing/release-configuration branch from b3d7ac1 to 1ea1608 Compare November 21, 2025 13:10
@euanh
Copy link
Collaborator

euanh commented Nov 21, 2025

Merged as part of #167

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/testing Improvements to tests.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants