Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
+++ This bug was initially created as a clone of Bug #1342683 +++
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
--- Additional comment from Antonio Murdaca on 2016-06-03 17:56:45 EDT ---
For completeness and as a reminder to me while testing - this is also working if we build projectatomic/docker locally.
--- Additional comment from Antonio Murdaca on 2016-06-03 18:28:48 EDT ---
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
--- Additional comment from Daniel Walsh on 2016-06-04 05:07:30 EDT ---
Seems strange that one of our patches would cause problems here?
--- Additional comment from Antonio Murdaca on 2016-06-04 05:14:27 EDT ---
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
--- Additional comment from Antonio Murdaca on 2016-06-07 06:57:53 EDT ---
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.
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.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2016:1274