Skip to content

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

Closed
jasonbrooks opened this issue Dec 12, 2018 · 13 comments
Closed

build failure with podman #254

jasonbrooks opened this issue Dec 12, 2018 · 13 comments

Comments

@jasonbrooks
Copy link

During the coreos-assembler build process on a Fedora 29 VM with nested kvm enabled, I'm getting a ton of cp: 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 a ModuleNotFoundError: No module named 'pytz' error -- I'll follow up on that separately).

dracut: FAILED: /usr/lib/dracut/dracut-install -D /tmp/dracut/dracut.HD3Ged/initramfs /usr/lib/dracut/modules.d/30ignition/ignition-files.service /usr/lib/systemd/system/ignition-files.service
cp: setting attributes for '/tmp/dracut/dracut.HD3Ged/initramfs/usr/lib/systemd/system/ignition-ask-var-mount.service': Operation not supported
dracut-install: ERROR: installing '/usr/lib/dracut/modules.d/30ignition/ignition-ask-var-mount.service' to '/usr/lib/systemd/system/ignition-ask-var-mount.service'
dracut: FAILED: /usr/lib/dracut/dracut-install -D /tmp/dracut/dracut.HD3Ged/initramfs /usr/lib/dracut/modules.d/30ignition/ignition-ask-var-mount.service /usr/lib/systemd/system/ignition-ask-var-mount.service
cp: setting attributes for '/tmp/dracut/dracut.HD3Ged/initramfs/lib/modules/4.19.8-300.fc29.x86_64//kernel/drivers/firmware/qemu_fw_cfg.ko.xz': Operation not supported
dracut-install: dracut_install 'qemu_fw_cfg' ERROR
dracut-install: ERROR: installing 'qemu_fw_cfg'
dracut: FAILED:  /usr/lib/dracut/dracut-install -D /tmp/dracut/dracut.HD3Ged/initramfs --kerneldir /lib/modules/4.19.8-300.fc29.x86_64/ -m qemu_fw_cfg
dracut: installkernel failed in module ignition
error: Finalizing rootfs: During kernel processing: Executing bwrap(rpmostree-dracut-wrapper): Child process killed by signal 1
@jlebon
Copy link
Member

jlebon commented Dec 12, 2018

ModuleNotFoundError: No module named 'pytz'

Ahh yeah, that one is likely a regression from #252.

@cgwalters
Copy link
Member

cp: setting attributes for '/tmp/dracut/dracut.HD3Ged/initramfs/usr/lib/systemd/system/ignition-ask-var-mount.service': Operation not supported

Is currently expected...it's a dracut bug that should be harmless.

@jlebon
Copy link
Member

jlebon commented Dec 12, 2018

#255

@dustymabe
Copy link
Member

#255

merged.

@dustymabe
Copy link
Member

error: Finalizing rootfs: During kernel processing: Executing bwrap(rpmostree-dracut-wrapper): Child process killed by signal 1

can you maybe attach a file to this ticket that is your full log output including the invocation using podman/docker ?

@jasonbrooks
Copy link
Author

jasonbrooks commented Dec 12, 2018

@jlebon
Copy link
Member

jlebon commented Dec 17, 2018

cp: setting attributes for '/tmp/dracut/dracut.D5H9tj/initramfs/lib/modules/4.19.8-300.fc29.x86_64//kernel/drivers/firmware/qemu_fw_cfg.ko.xz': Operation not supported
dracut-install: dracut_install 'qemu_fw_cfg' ERROR
dracut-install: ERROR: installing 'qemu_fw_cfg'

Hmm, yeah this looks like dracut's cp failing to copy xattrs.

This is with podman, but with docker the operation goes further

Can you paste the outputs of findmnt inside the container for the two? Looks like the difference might be podman setting a tmpfs on /tmp?

Alternatively, you might also want to try the new rootless backend, see #236 (comment).

@cgwalters
Copy link
Member

I think the problem here has to do with /var/tmp. I can't reproduce this in my devshell but I can with the official container + alias.

I think rpm-ostree should always use a tmpdir under the target root; but looking at this now.

cgwalters added a commit to cgwalters/rpm-ostree that referenced this issue Dec 17, 2018
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
@cgwalters
Copy link
Member

PR in coreos/rpm-ostree#1716

rh-atomic-bot pushed a commit to coreos/rpm-ostree that referenced this issue Dec 17, 2018
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
rh-atomic-bot pushed a commit to coreos/rpm-ostree that referenced this issue Dec 17, 2018
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
rh-atomic-bot pushed a commit to coreos/rpm-ostree that referenced this issue Dec 17, 2018
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
rh-atomic-bot pushed a commit to coreos/rpm-ostree that referenced this issue Dec 17, 2018
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
@dustymabe
Copy link
Member

PR in projectatomic/rpm-ostree#1716

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.

cgwalters added a commit to cgwalters/machine-config-operator that referenced this issue Dec 18, 2018
This matches what the main build does; also happens to work around
coreos/coreos-assembler#254
@miabbott
Copy link
Member

I just ran into this after updating my Silverblue host:

podman 1:0.10.1.3-4.gitdb08685.fc29 -> 1:0.12.1.1-1.git66d3499.fc29

But the latest quay.io/coreos-assembler/coreos-assembler build that @dustymabe did fixed it for me 👍

@jasonbrooks
Copy link
Author

This is working for me now -- I'm most of the way through a build w/ podman. I pulled the latest image this afternoon.

@jlebon
Copy link
Member

jlebon commented Dec 19, 2018

Cool, closing this issue then!

@jlebon jlebon closed this as completed Dec 19, 2018
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

No branches or pull requests

5 participants