-
-
Notifications
You must be signed in to change notification settings - Fork 5
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
Alpine version update? #46
Comments
Hi, I think it was suggested that we'd use alpine when we started out with the test runners, to keep the image size small. I have no idea why I pinned 3.10 though. I probably used an example from somewhere and didn't think about the version. We should probably update that to latest. Since alpine has got everything needed for the test runner, I don't really see a reason to switch to Ubuntu, but feel free to make the switch if you think it's better. |
Yep. That and the fact that Alpine is a very secure base image makes it our preferred
Pinning of images in general is a good thing, as it makes the Docker image behave more predictable.
What will be the difference between CI and the test runner? Is there anything that is different from Ubuntu to Alpine? |
I'm not clear if there is a difference TBH. But I was thinking it would narrow down any delta between what the track's CI tests (using Ubuntu on GitHub's workflow runners) and what the students experience. Hopefully helping to reduce any issues like exercism/c#699 I'm still not really sure what is causing that issue, but reducing the delta might help to narrow down the possibilities. |
Do you have any indication of the size difference between an Ubuntu-based vs Alpine-based image? |
Hi there,
Is there any specific reason that the Dckerfile uses Alpine pinned at version 3.10 ?
That security support for that version finished 6 months ago.
Follow-up question: is there any specific reason to stick with Alpine at all?
All the track CI uses Ubuntu 18.04 at the moment (update to 20.04 is in the works), so this would be a point of difference between how the website runs submissions and how the track is created.
Tagging @bergjohan as you created it the Dockerfile.
Tagging @ErikSchierboom as I think you probably have the view from the test-runner specification.
The text was updated successfully, but these errors were encountered: