-
Notifications
You must be signed in to change notification settings - Fork 328
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
If the main image includes multiple base images, a common file in base images causes build failure #3342
Comments
Attached file (which includes checkout out mkosi binaries too) is the compressed layout of the configuration. |
When copying a directory from or to an image, let's always merge with existing directories instead of failing with "File Exists". Fixes systemd/mkosi#3342.
@utezduyar The linked PR should fix your issue. But please don't use Format=disk for base images, you Format=directory instead. Then you don't have to run everything as root. |
Thank you. I verified that your patch fixes it by replacing your version of systemd-dissect in mkosi.output/tools. Do you have any tips on how I can proceed while waiting for a new systemd release? I don't want to distribute tools tree with my mkosi.conf. I couldn't find any hooks in Tools*= configs. Also, thank you for the Format=disk tip. I will change it. |
Just changing to Format=directory for your base images will fix the problem as well. |
mkosi commit the issue has been seen with
mkosi 25~devel
Used host distribution
Debian
Used target distribution
Debian
Linux kernel version used
6.1.0-21-amd64
CPU architectures issue was seen on
x86_64
Unexpected behaviour you saw
I have 3 base images, common, device-management and webrtc-streaming. The device-management and webrtc-streaming images are based on common. The main image is based on device-management and webrtc-streaming.
The build fails due to conflict and my guess is that because of the common part of both device-management and webrtc-streaming.
Used mkosi config
mkosi output
The text was updated successfully, but these errors were encountered: