-
Notifications
You must be signed in to change notification settings - Fork 173
build failure with podman #254
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Ahh yeah, that one is likely a regression from #252. |
Is currently expected...it's a dracut bug that should be harmless. |
merged. |
can you maybe attach a file to this ticket that is your full log output including the invocation using podman/docker ? |
@dustymabe Yeah, I'm re-running it https://paste.fedoraproject.org/paste/kSK6ErnDUkdTUYF9OP2DEw |
Hmm, yeah this looks like dracut's
Can you paste the outputs of Alternatively, you might also want to try the new rootless backend, see #236 (comment). |
I think the problem here has to do with I think rpm-ostree should always use a tmpdir under the target root; but looking at this now. |
The problem here is that bare-user has `user.ostreemeta` xattrs, `tmpfs` (which bwrap uses for `/var/tmp` by default) doesn't support that. Pass through the tmpdir to the target rootfs, which is the same place as the repo in unified-core mode. Ref: coreos/coreos-assembler#254
PR in coreos/rpm-ostree#1716 |
The problem here is that bare-user has `user.ostreemeta` xattrs, `tmpfs` (which bwrap uses for `/var/tmp` by default) doesn't support that. Pass through the tmpdir to the target rootfs, which is the same place as the repo in unified-core mode. Ref: coreos/coreos-assembler#254 Closes: #1716 Approved by: jlebon
The problem here is that bare-user has `user.ostreemeta` xattrs, `tmpfs` (which bwrap uses for `/var/tmp` by default) doesn't support that. Pass through the tmpdir to the target rootfs, which is the same place as the repo in unified-core mode. Ref: coreos/coreos-assembler#254 Closes: #1716 Approved by: jlebon
The problem here is that bare-user has `user.ostreemeta` xattrs, `tmpfs` (which bwrap uses for `/var/tmp` by default) doesn't support that. Pass through the tmpdir to the target rootfs, which is the same place as the repo in unified-core mode. Ref: coreos/coreos-assembler#254 Closes: #1716 Approved by: cgwalters
The problem here is that bare-user has `user.ostreemeta` xattrs, `tmpfs` (which bwrap uses for `/var/tmp` by default) doesn't support that. Pass through the tmpdir to the target rootfs, which is the same place as the repo in unified-core mode. Ref: coreos/coreos-assembler#254 Closes: #1716 Approved by: cgwalters
there is a new build of coreos-assembler I kicked off this morning that should have this fix if anyone wants to try things again. |
This matches what the main build does; also happens to work around coreos/coreos-assembler#254
I just ran into this after updating my Silverblue host:
But the latest quay.io/coreos-assembler/coreos-assembler build that @dustymabe did fixed it for me 👍 |
This is working for me now -- I'm most of the way through a build w/ podman. I pulled the latest image this afternoon. |
Cool, closing this issue then! |
During the
coreos-assembler build
process on a Fedora 29 VM with nested kvm enabled, I'm getting a ton ofcp: setting attributes for XXX: Operation not supported
errors before the operation errors out. This is with podman, but with docker the operation goes further (It's stopping much later on, with aModuleNotFoundError: No module named 'pytz'
error -- I'll follow up on that separately).The text was updated successfully, but these errors were encountered: