-
Notifications
You must be signed in to change notification settings - Fork 34
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
docker: add ability to build with docker #7
base: master
Are you sure you want to change the base?
Conversation
Hi @dtrunk90, thanks for the patch. However I cannot accept it in the current state because it:
I am already working on automated builds through Gitea actions and a VM-based runner, which are working, but need some cleanup before it is fully ready (see master...gitea-actions#files_bucket). All "clean" container-based build attempts I made this far, fail at some point because of limitations in the way
In the end, yes, you do. Whether it is from a container running the target distribution, or from a VM running the target distribution. This is how I build ISO images currently - launch a dedicated libvirt/qemu VM, clone the repository inside it and run the Makefile from there. This also provides more isolation compared to a container. The ongoing work on Gitea actions just automates this a little bit more, and I'm not in a hurry since I only actually rebuild when new Debian releases are made. Though I could probably rebuild on every point release. You could probably just I will keep this open for future reference, but don't expect a merge soon. Thanks again |
yeah, i just meant you don't need to install a whole debian system first or use a vm or a live system or whatever
¹ Nope, unfortunately it is required for mounting to work:
|
I will try to rework this to make it work with (rootful, no choice) podman |
With docker we don't need to build from the same distribution as the target distribution.
Tested on Ubuntu 20.04.6 LTS