-
-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve devcontainer build speed #8
Comments
The below is extracted from the logs, the main Notably, no output is produced for ~12 minutes (730 seconds). "Fedora 40 - aarch64 - Updates" then takes another 6 minutes (370 seconds). In the second cc @hroncok for any advice (as author of python/cpython#103283)
|
That's pretty bad, but I have no idea why would it take so long. Perhaps it's the emulation/virtualization that is there that is so slow? |
I was having a quick nosey here 👋🏽 but looking at the Actions runs, the build is taking |
This should be faster, see https://fedoraproject.org/wiki/Changes/ReplaceDnfWithDnf5 > Significantly faster for many user cases > Optimization of download metadata Fedora 41 is currently still in beta, but if this causes trouble, we can always revert. Related to python#8
The repository is enabled by default but we don't need it. By explicitly disabling it, we prevent unnecessary metadata fetch. Related to python#8
* Update to Fedora 41 with dnf5 This should be faster, see https://fedoraproject.org/wiki/Changes/ReplaceDnfWithDnf5 > Significantly faster for many user cases > Optimization of download metadata Fedora 41 is currently still in beta, but if this causes trouble, we can always revert. Related to #8 * Disable extra repository with a multimedia codec The repository is enabled by default but we don't need it. By explicitly disabling it, we prevent unnecessary metadata fetch. Related to #8
Ah that makes sense. Will have a look over there and maybe do some digging on why this is taking so long then. |
Last release by Brett took 28 mins. |
What do you think about splitting actual container creation into two steps? One with big |
I'm personally fine with that if @corona10 and @erlend-aasland are. I have #12 open to split things up in regards to WASI, but I wasn't sure about following through with it due to having to change the CPython repo when new containers go out. We might need to settle on some policy in #11 to know how much work would be expected. |
+1 |
+1 |
@brettcannon
The 35-minute release period is pretty painful. We may need to find out whether we can reduce the build time.
https://github.com/python/cpython-devcontainers/actions/runs/11038928730
The text was updated successfully, but these errors were encountered: