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
Because our production image building runs inside a container (privileged though), we can't use kpartx as it attempts to mess with device-mapper which is very very unpleasant to use inside containers.
We do however have working loop devices, so using losetup would be fine.
So we need to change distrobuilder to scan the partition table of the .img file, figure out the offset and size of the partition we want and then map that using losetup, then mount it.
The text was updated successfully, but these errors were encountered:
Because our production image building runs inside a container (privileged though), we can't use
kpartx
as it attempts to mess with device-mapper which is very very unpleasant to use inside containers.We do however have working loop devices, so using
losetup
would be fine.So we need to change distrobuilder to scan the partition table of the .img file, figure out the offset and size of the partition we want and then map that using
losetup
, then mount it.The text was updated successfully, but these errors were encountered: