Skip to content
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

Fix go runtime image #135

Merged
merged 1 commit into from
May 16, 2022
Merged

Fix go runtime image #135

merged 1 commit into from
May 16, 2022

Conversation

coffee-cup
Copy link
Contributor

Run go code in debian slim, not the nixpacks debian image

@@ -0,0 +1,3 @@
pub static DEFAULT_BASE_IMAGE: &str = "ghcr.io/railwayapp/nixpacks:debian-1652414952";
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think we should be pinning it to a specific version.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why not? The base image is stored in the build plan and makes builds more reproducible. If it just uses the latest image then an update may break the build.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Whenever a new version of the image goes out, we have to manually change the source code. I don't think this is a good idea (perhaps we can make it auto-update?)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah thats true, but it means we are being explicit about the image. Alternatively we could fetch the latest when nixpacks is run and then use that in the build plan. But that can come in a separate PR.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Going to merge this for now since I prefer being explicit and pinning the dep over always pulling the latest. At least when it comes to the build plan generated.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah thats true, but it means we are being explicit about the image. Alternatively we could fetch the latest when nixpacks is run and then use that in the build plan. But that can come in a separate PR.

I'd be happy to implement this. Just a quick question, how can we make it so that it is still reproducible?

@coffee-cup coffee-cup merged commit c6d3eb9 into main May 16, 2022
@coffee-cup coffee-cup deleted the jr/fix-go-run-image branch May 16, 2022 17:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants