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
The problem arise when something inside the sysbox container is trying to chown devices in /dev. For instance, when i use the following Dockerfile
FROM registry.suse.com/suse/sle15:15.5
RUN zypper update -y
If SUSE base image is not latest version and contain outdated version of permissions package, zypper package manager will update it and permissions package will try to execute chown root:root on all devices in /dev that are not owned by root:
This leads docker build to fail with an error exit code. Of course this can be avoided by using latest SUSE base image where permissions package is already updated, but it's not always possible. I read the sysbox docs and found some useful feature to ignore chown of /sys: https://github.com/nestybox/sysbox/blob/master/docs/user-guide/configuration.md#ignoring-chowns-of-sysfs
My question: is it possible to add the same feature for chowns of /dev?
The text was updated successfully, but these errors were encountered:
Hello,
The problem arise when something inside the sysbox container is trying to chown devices in /dev. For instance, when i use the following Dockerfile
If SUSE base image is not latest version and contain outdated version of
permissions
package, zypper package manager will update it andpermissions
package will try to executechown root:root
on all devices in /dev that are not owned by root:This leads docker build to fail with an error exit code. Of course this can be avoided by using latest SUSE base image where permissions package is already updated, but it's not always possible. I read the sysbox docs and found some useful feature to ignore chown of /sys: https://github.com/nestybox/sysbox/blob/master/docs/user-guide/configuration.md#ignoring-chowns-of-sysfs
My question: is it possible to add the same feature for chowns of /dev?
The text was updated successfully, but these errors were encountered: