GH-45156: [Python][Packaging] Refactor Python Windows wheel images to use newer base image #45442
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This is failing when the image is built with a thrift checksum mismatch from vcpkg but otherwise what's here in the PR is working. |
|
I let a build of the base image run overnight and it ran out of disk space on my small hard disk but it looks like it built. So next steps here are:
|
amoeba
force-pushed
the
feature/GH-45156--python-windows-wheel-docker-image
branch
from
9c311c3 to
0c18bee
Compare
amoeba
force-pushed
the
feature/GH-45156--python-windows-wheel-docker-image
branch
from
0c18bee to
ed31241
Compare
|
Good progress today. I was able to build the base image with a combination of increasing the memory limit to 4GB and tweaking the storage limit. I propagated the changes to the other dockerfiles and elsewhere in the repo. Now this just needs testing. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Rationale for this change
See #45156.
What changes are included in this PR?
Mostly just stashing my changes here as I work on migrating the existing Dockerfiles to the new base.
Are these changes tested?
TODO
Are there any user-facing changes?
TODO