-
Notifications
You must be signed in to change notification settings - Fork 21
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
A more minimal container image based on Alpine #188
Conversation
Hi there! Thanks for the PR 👍 I agree that an Alpine based image is probably better suited for production use (attack surface, size, ...). However, the Debian based image is useful to make sure that openwec works well on Debian systems, and it better mimics a typical server environment for demo/test purposes. I suggest keeping both images with separate tags:
Still, it would be great to keep What do you think? |
Perfect. Thank you :) |
Preparation for a minimal Alpine-based image.
The images can be used by all OCI-standard implementations. The only Docker-specific entity around the images is the Dockerfile, but the images themselves work perfectly with Podman, containerd, CRI-O, Docker.
Done. I've updated the PR description. I used slightly different naming, which conforms to how the Docker |
A question: Don't you want to get rid of the letter https://github.com/docker/metadata-action?tab=readme-ov-file#typesemver For example:
|
Preparation for a second Alpine-based image.
Yes! The letter |
Thank you very much! 👍 |
This is a "Request for Comments" PR about adding a more minimalistic Alpine-based container image.
My motivation is dual:
The new tagging mechanism looks like this (I've created a tag
v0.3.0-machinefilter
in my fork):Image sizes:
Installed packages:
Alpine: 20
Debian: 94
Alpine-based image:
Click here to expand
Debian-based image:
Click here to expand
Unfortunately, I couldn't use the official
rust:alpine*
image as I hit different issues withbindgen
and dynamic/static linking; so everything is based on an Alpine base image.