Bug 1772377 - buildah error lsetfilecon Operation not supported
Summary: buildah error lsetfilecon Operation not supported
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: rpm
Version: 31
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Packaging Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1845168
TreeView+ depends on / blocked
 
Reported: 2019-11-14 09:44 UTC by llegolas
Modified: 2020-11-24 18:17 UTC (History)
16 users (show)

Fixed In Version:
Clone Of:
: 1845168 (view as bug list)
Environment:
Last Closed: 2020-11-24 18:17:00 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
buildah script (674 bytes, application/x-shellscript)
2019-11-14 09:44 UTC, llegolas
no flags Details

Description llegolas 2019-11-14 09:44:36 UTC
Created attachment 1636074 [details]
buildah script

Description of problem:
buildah form scratch spits out a lot of errors similar to:
error: lsetfilecon: (/usr/share/man/man8/rtacct.8.gz;5dcd1986, system_u:object_r:man_t:s0) Operation not supported

setting virt_sandbox_use_fusefs on or off selinux boolean has no affect.

Version-Release number of selected component (if applicable):buildah-1.11.4-2.fc31.x86_64


How reproducible: all the time


Steps to Reproduce:
1.buildah unshare bash fedora-31-base.sh
  the buildah script is in the attachment;

Actual results:
the resulting image runs fine but the error messages are annoying and perhaps indication for missconfiguration 

Expected results:

no error messages in the output
Additional info: fresh install of f31

Comment 1 llegolas 2019-11-14 09:47:40 UTC
I am pretty sure the same script run w/o the err on f30

Comment 2 Daniel Walsh 2019-11-16 21:28:25 UTC
This looks like the issue is the dnf command is attempting to put down SELinux labels within the rootfs.  And this must be on a file system that does not support labels?

Comment 3 Daniel Walsh 2019-11-16 21:28:57 UTC
BTW this line
buildah commit $container fedora-29-base

needs to be updated in your script.

Comment 4 llegolas 2019-11-16 22:59:13 UTC
The containers/storage.conf has overlay as driver. The underlying fs (my $HOME) is ext4 but it behaves the same on XFS on my other system. Both are mounted with default fedora flags.
As for the script - indeed it needs update.

Comment 5 llegolas 2019-11-21 10:02:30 UTC
I managed to narrow it a bit down.
the script from above works fine on vanilla f29 and f30 (both updated to the latest as of today).
It breaks with f31 booted with both f30 and f31 kernels kernel-core-5.3.11-100.fc29.x86_64 and kernel-core-5.3.11-300.fc31.x86_64 respectively.

Seem like problem is somewhere in userspace.

Comment 6 Derrick Ornelas 2020-06-16 22:38:14 UTC
Bug 1777502 indicates that this is an rpm issue.

Comment 7 Ben Cotton 2020-11-03 17:14:05 UTC
This message is a reminder that Fedora 31 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '31'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 31 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 8 Ben Cotton 2020-11-24 18:17:00 UTC
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.