Closed hanskuhn closed 8 months ago
Ah, your system but be an old Ubuntu release which was updated to Ubuntu 20.04 as Ubuntu 20.04 ships with /bin being a symlink to /usr/bin so this wouldn't have been a problem.
Anyway, as /bin is a symlink to /usr/bin on all modern systems, there's no real harm in using /bin/mkdir so I'll be doing that now.
Fix pushed to daily and stable packaging repos (zabbly/incus), it will take a few days before it rolls out to users.
Ah, your system but be an old Ubuntu release which was updated to Ubuntu 20.04 as Ubuntu 20.04 ships with /bin being a symlink to /usr/bin so this wouldn't have been a problem.
Anyway, as /bin is a symlink to /usr/bin on all modern systems, there's no real harm in using /bin/mkdir so I'll be doing that now.
Yep! The VM was an 18.04 that got upgraded to 20.04. Good sleuthing. Thanks for all the great work!
Hi! Thanks for the awesome work to keep my favorite container software alive. I've started to migrate from LXD to Incus and ran into a hiccup. I was able to work around my problem, but wanted to share my experience in case it's useful. Let me know if more information is needed.
Thanks!
Required information
Issue description
This is a conversion from LXD -> Incus using the lxd-to-incus script. The
incus-lxcfs.service
fails to start because 'mkdir' isn't found.I confirmed that a symlink from /bin/mkdir to /usr/bin/mkdir fixes the problem and allows the
incus-lxcfs.service
to start.I looked at the
coreutils
pkg and it appears that /bin/mkdir is the expected location for this binary.Steps to reproduce
lxd-to-incus
journalctl -u incus-lxcfs.service
to see the error when mkdir isn't found.Information to attach