-
Notifications
You must be signed in to change notification settings - Fork 0
fix: Update to new registry and refactor: slim down image #23
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
Conversation
7db6b50 to
4a00fd3
Compare
|
We should open a separate issue about this, but given how much of this is package caching and such, I wonder if we could effectively use the fancy cache mounting features and a GitHub action cache to speed up the builds (and slim down the resulting images). |
28c3839 to
812ef7a
Compare
e0ad686 to
6f9529b
Compare
533d9a7 to
ed0d976
Compare
ed0d976 to
6c904ff
Compare
tlater-famedly
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like this a lot, let's get it merged ASAP and stop wasting storage and CI credits :D
tlater-famedly
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just actually noting this in review so we don't merge this before it's approved - cargo-binstall isn't on our allowed software source list, but we've started the process.
|
The ghcr incompatibility is most likely because the REGISTRY_PASSWORD is set now (instead of NEXUS_PASSWORD or HARBOUR_PASSWORD) |
betarustup toolchain channeluse action to build image for ghcr registryOur docker flow seems not work anymore with ghcr.io