Skip to content

bib: mount devtmpfs inside the container too#238

Merged
cgwalters merged 2 commits intoosbuild:mainfrom
mvo5:mount-devtmpfs
Mar 6, 2024
Merged

bib: mount devtmpfs inside the container too#238
cgwalters merged 2 commits intoosbuild:mainfrom
mvo5:mount-devtmpfs

Conversation

@mvo5
Copy link
Contributor

@mvo5 mvo5 commented Mar 6, 2024

This ensures that the new partscan feature in osbuild works. By default the containers only have a static snapshot of /dev on a tmpfs. This means that anything later added by losetup will be missing inside the container.

It also means that osbuild/osbuild#1468 can be reverted.

This should unblock #120 and also osbuild/images#462

mvo5 added a commit to mvo5/osbuild that referenced this pull request Mar 6, 2024
This reverts commit 158acaa.

With osbuild/bootc-image-builder#238 the
original reason to call mknod goes away so we can just revert
it. osbuild now requires not only the loop device but also uses
`losetup --partscan` quite a lot now so the mknod approach becomes
impractical and the consumers of osbuild in a container should
just setup devtmpfs.
@cgwalters
Copy link
Contributor

Tempting to merge over red because we know this can't break the ISO...

@cgwalters
Copy link
Contributor

Ah man, shouldn't have clicked the "merge main" button, I thought it was fast forward. I assume we don't want merge commits in this repo.

mvo5 added 2 commits March 6, 2024 14:44
This ensures that the new `partscan` feature in osbuild works. By
default the containers only have a static snapshot of /dev on a
tmpfs. This means that anything later added by losetup will be
missing inside the container.

It also means that osbuild/osbuild#1468
can be reverted.
@cgwalters cgwalters added this pull request to the merge queue Mar 6, 2024
Merged via the queue into osbuild:main with commit e1cf3df Mar 6, 2024
mvo5 added a commit to mvo5/osbuild that referenced this pull request Mar 11, 2024
This reverts commit 158acaa.

With osbuild/bootc-image-builder#238 the
original reason to call mknod goes away so we can just revert
it. osbuild now requires not only the loop device but also uses
`losetup --partscan` quite a lot now so the mknod approach becomes
impractical and the consumers of osbuild in a container should
just setup devtmpfs.
bcl pushed a commit to mvo5/osbuild that referenced this pull request Mar 12, 2024
This reverts commit 158acaa.

With osbuild/bootc-image-builder#238 the
original reason to call mknod goes away so we can just revert
it. osbuild now requires not only the loop device but also uses
`losetup --partscan` quite a lot now so the mknod approach becomes
impractical and the consumers of osbuild in a container should
just setup devtmpfs.
bcl pushed a commit to mvo5/osbuild that referenced this pull request Mar 13, 2024
This reverts commit 158acaa.

With osbuild/bootc-image-builder#238 the
original reason to call mknod goes away so we can just revert
it. osbuild now requires not only the loop device but also uses
`losetup --partscan` quite a lot now so the mknod approach becomes
impractical and the consumers of osbuild in a container should
just setup devtmpfs.
achilleas-k pushed a commit to osbuild/osbuild that referenced this pull request Mar 13, 2024
This reverts commit 158acaa.

With osbuild/bootc-image-builder#238 the
original reason to call mknod goes away so we can just revert
it. osbuild now requires not only the loop device but also uses
`losetup --partscan` quite a lot now so the mknod approach becomes
impractical and the consumers of osbuild in a container should
just setup devtmpfs.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants