Skip to content

Installation: kiwi image builder fails (build containers lack systemd) #3746

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

Open
itoffshore opened this issue Apr 26, 2025 · 0 comments
Open

Comments

@itoffshore
Copy link

itoffshore commented Apr 26, 2025

Describe the problem

I see this while building an image using kiwi in podman - so perhaps it happens with other Linux image flavours besides Tumbleweed (& will also happen in build environments under docker)

installation under MicroOS (tumbleweed) in a clean build container environment fails:

 Post Install of an clean install
open /etc/init.d/netbird: no such file or directory
Error: open /etc/init.d/netbird: no such file or directory
exit status 1
Error: exit status 1

To Reproduce

zypper in netbird

Expected behavior

tumbleweed uses systemd so /etc/init.d should not be looked for. I suspect due to building an image inside a container a legacy non systemd Linux is assumed.

Perhaps check for /lib/systemd existing rather than the presence of the systemd binary (which will be missing from images running under docker & podman)

Are you using NetBird Cloud?

Netbird Cloud

netbird version

0.43.0


Netbird has been running perfectly under MicroOS for about 9 months now as an rpm

@itoffshore itoffshore changed the title Installation: kiwi image builder fails (/etc/init.d not used in tumbleweed) Installation: kiwi image builder fails (build containers lack systemd) Apr 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant