Bug 1342683 - Untar re-exec error: exit status 1: output: operation not supported
Summary: Untar re-exec error: exit status 1: output: operation not supported
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: docker
Version: 25
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Antonio Murdaca
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1343702
TreeView+ depends on / blocked
 
Reported: 2016-06-03 21:39 UTC by Adam Miller
Modified: 2017-12-12 10:41 UTC (History)
13 users (show)

Fixed In Version:
Clone Of:
: 1343702 (view as bug list)
Environment:
Last Closed: 2017-12-12 10:41:05 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Adam Miller 2016-06-03 21:39:43 UTC
Description of problem:
# docker --debug=true build -t fedora:24 .                                                           
Sending build context to Docker daemon 315.1 MB
Step 1 : FROM scratch
 ---> 
Step 2 : MAINTAINER Adam Miller <maxamillion>
 ---> Using cache
 ---> dd64eef9ba1f
Step 3 : ADD fedora-24-20160602.tar /
Untar re-exec error: exit status 1: output: operation not supported



Version-Release number of selected component (if applicable):
docker-1.11.1-5.git9dea74f.fc25.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Download https://kojipkgs.fedoraproject.org//work/tasks/111/14350111/Fedora-Docker-Base-24-20160602.n.0.x86_64.tar.xz
2. tar -xvJf Fedora-Docker-Base-24-20160602.n.0.x86_64.tar.xz
3. 87fab38d658cbbd99872ce3c817dd7e11d9274916dd9f40601b91ca0c9bfb1c5/layer.tar fedora-24-20160602.tar
4. xz --compress fedora-24-20160602.tar
5. cat > Dockerfile <<-EOF
FROM scratch
MAINTAINER Adam Miller <maxamillion>
ADD fedora-24-20160602.tar /
EOF
6. docker build -t fedora:24 .


Additional info:

This has been discussed upstream:
https://github.com/docker/docker/issues/20331

It works if you build from upstream sources:
https://github.com/docker/docker/issues/20331#issuecomment-223677761
 and confirmed to work

Comment 1 Antonio Murdaca 2016-06-03 21:56:45 UTC
For completeness and as a reminder to me while testing - this is also working if we build projectatomic/docker locally.

Comment 2 Antonio Murdaca 2016-06-03 22:28:48 UTC
looks like 1.10.3 is working fine though:

$ docker build -t fedora:24 .
Sending build context to Docker daemon 268.9 MB
Step 1 : FROM scratch
 ---> 
Step 2 : ADD fedora-24-20160602.tar.xz /
 ---> 88499dae83f5
Removing intermediate container 73352c250138
Successfully built 88499dae83f5

$ docker run -ti fedora:24 bash
[root@45f1a3d56623 /]# cat /etc/os-release 
NAME=Fedora
VERSION="24 (Twenty Four)"
ID=fedora
VERSION_ID=24
PRETTY_NAME="Fedora 24 (Twenty Four)"
ANSI_COLOR="0;34"
CPE_NAME="cpe:/o:fedoraproject:fedora:24"
HOME_URL="https://fedoraproject.org/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Fedora"
REDHAT_BUGZILLA_PRODUCT_VERSION=24
REDHAT_SUPPORT_PRODUCT="Fedora"
REDHAT_SUPPORT_PRODUCT_VERSION=24

Comment 3 Daniel Walsh 2016-06-04 09:07:30 UTC
Seems strange that one of our patches would cause problems here?

Comment 4 Antonio Murdaca 2016-06-04 09:14:27 UTC
The failure with docker 1.11.1 can be legit though (much stuff going on with runc and containerd integration and we setup containerd differently than upstream so it might be this). I've built 1.11.2 for rawhide just yesterday also.

I'd like Adam to test this out with 1.10.3 from updates-testing in Fedora 23 (or with Fedora 24 which already has 1.10.3).

I'll take a closer look in rawhide

Comment 5 Antonio Murdaca 2016-06-07 10:57:53 UTC
On a F24 box - building docker 1.11.2 from projectatomic/docker branch docker-1.11 works fine. I'm gonna test with Rawhide soon.

Comment 6 Antonio Murdaca 2016-06-07 19:43:50 UTC
Found it - the "--selinux-enabled" flag is causing the

Untar re-exec error: exit status 1: output: operation not supported

This is indeed the only difference between upstream unit file and us :)

I'm going to look deeper into fixing this.

Comment 7 Antonio Murdaca 2016-06-07 19:46:10 UTC
For some reason, Selinux isn't complaining at all - it's just the "--selinux-enabled" flag which is causing this!

Comment 8 Antonio Murdaca 2016-06-08 09:49:25 UTC
Fix for Fedora https://github.com/projectatomic/docker/pull/165

Comment 9 Daniel Walsh 2016-06-09 14:28:05 UTC
The problem here is not an SELinux denial. The problem is the kernel does not allow processes to assign contexts via INODE if the mount point uses a context mount.  Since docker does a context mount when using devicemapper and selinux together, the tar attempting to write an SELinux label is being blocked by an ENOTSUPP error.  Docker should ignore this error and write the file.  The patch above basically does this.

Comment 10 Adam Miller 2016-07-07 17:26:11 UTC
FWIW, this appears to be resolved in Fedora 23, 24 and Rawhide .... it might still be an issue upstream though, just wanted to report that builds that were broken for me are no longer broken.

Comment 11 Antonio Murdaca 2016-07-07 17:30:45 UTC
awesome, upstream fixed this also (it was already fixed tbh)

Comment 12 Jan Kurik 2016-07-26 04:04:07 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 25 development cycle.
Changing version to '25'.

Comment 13 Fedora End Of Life 2017-11-16 19:24:01 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. 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 '25'.

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 25 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 14 Fedora End Of Life 2017-12-12 10:41:05 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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.