-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Introduce thin and full docker images #2090
base: develop
Are you sure you want to change the base?
Conversation
@tboerger what reason to create one more image with |
If needed we can create separate image based on |
Cargo is for sure required for cryptography and this is also some dependency of other packages installed within the image. As describe on chat the thin image stays with the same tag as before, just for giving more flexibility to customize the semaphore image there is the customize tag. The customize tag starts as root user, which makes it possible to install alpine packages via packages.txt and it also starts with base-build and cargo for being able to install nearly any python dependency. Later on in the start process it's using su-exec to drop the privileges for running the semaphore process. |
I'm understood why I planning to use this way for creating multiple images for |
7a41d93
to
e2e8f66
Compare
I'm currently experimenting with the installed tools a little bit to get a good image size. I would suggest to simply use the Alpine package for Ansible for the slim version and using pip maybe only within the custom tag as this will boost the container size. In the end the user can choose one of the images depending on how much he wants to customize it. |
The current state WITH python-dev reaches 843MB. Without python-dev you are not able to install so many oython deps... Than we could directly drop the requirements.yml entirely from the slim image and preinstall a specific subset of python modules from Alpine packages only. |
No description provided.