You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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 underdocker
)installation under MicroOS (tumbleweed) in a clean build container environment fails:
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 nonsystemd
Linux is assumed.Perhaps check for
/lib/systemd
existing rather than the presence of thesystemd
binary (which will be missing from images running underdocker
&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
The text was updated successfully, but these errors were encountered: