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.
Description of problem:
When trying to build a Docker images using the 'busybox' base image, the user may receive an error like "image ID '' is invalid".
Version-Release number of selected component (if applicable):
docker-1.8.2-10.el7.x86_64
How reproducible:
Sporadic.
Steps to Reproduce:
1. Create Dockerfile that contains 'FROM busybox'
2. docker build -t <name> <path/to/Dockerfile>
Actual results:
-bash-4.2# docker build -t busybox_httpd /root/busybox_httpd/
Sending build context to Docker daemon 2.048 kB
Step 0 : FROM busybox
image ID '' is invalid
Expected results:
-bash-4.2# docker build -t busybox_httpd /root/busybox_httpd/
Sending build context to Docker daemon 2.048 kB
Step 0 : FROM busybox
Trying to pull repository registry.access.redhat.com/busybox ... not found
Trying to pull repository docker.io/library/busybox ... latest: Pulling from library/busybox
9e77fef7a1c9: Pull complete
964092b7f3e5: Pull complete
library/busybox:latest: The image you are pulling has been verified. Important: image verification is a tech preview feature and should not be relied on to provide security.
Digest: sha256:c1bc9b4bffe665bf014a305cc6cf3bca0e6effeb69d681d7a208ce741dad58e0
Status: Downloaded newer image for docker.io/busybox:latest
...
Additional info:
I've observed this sporadically while testing on RHELAH. Unfortunately, I have not been able to reliably reproduce this.
I have an Ansible playbook that attempts to build and run Docker images using a number of base images. In the most recent attempt to run the playbook, the first image build/run was successful using the 'alpine' base image. However, the follow on build/run of 'busybox' failed.
Below are some details from the system where I last saw the issue.
-bash-4.2# atomic host status
TIMESTAMP (UTC) VERSION ID OSNAME REFSPEC
* 2016-02-05 17:06:13 7.2.2 b1012093ef rhel-atomic-host rhel-atomic-host-ostree:rhel-atomic-host/7/x86_64/standard
2015-11-10 16:11:46 7.2 ec85fba1bf rhel-atomic-host rhel-atomic-host-ostree:rhel-atomic-host/7/x86_64/standard
-bash-4.2# rpm -q docker
docker-1.8.2-10.el7.x86_64
-bash-4.2# cat /root/busybox_httpd/Dockerfile
FROM busybox
MAINTAINER Micah Abbott <micah>
LABEL Version=1.0
LABEL RUN="docker run -d --name NAME -p 80:80 IMAGE"
ENV container docker
COPY Dockerfile /
RUN mkdir /www && echo "SUCCESS busybox_httpd" > /www/index.html
EXPOSE 80
ENTRYPOINT [ "/bin/httpd" ]
CMD [ "-f", "-h", "/www", "-p", "80" ]
-bash-4.2# docker build -t busybox_httpd /root/busybox_httpd/
Sending build context to Docker daemon 2.048 kB
Step 0 : FROM busybox
image ID '' is invalid
# journalctl -e --no-pager -u docker
...
Feb 10 16:14:45 dhcp-41-112.bos.redhat.com docker[4867]: time="2016-02-10T16:14:45.310791764-05:00" level=info msg="GET /v1.20/images/json"
Feb 10 16:14:45 dhcp-41-112.bos.redhat.com docker[4867]: time="2016-02-10T16:14:45.328533955-05:00" level=warning msg="couldn't load b175bcb790231169e232739bd2172bded9669c25104a9b723999c5f366ed7543 from docker.io/busybox:latest: image ID '' is invalid"
Feb 10 16:14:46 dhcp-41-112.bos.redhat.com docker[4867]: time="2016-02-10T16:14:46.155999154-05:00" level=info msg="POST /v1.20/build?cgroupparent=&cpuperiod=0&cpuquota=0&cpusetcpus=&cpusetmems=&cpushares=0&dockerfile=Dockerfile&memory=0&memswap=0&rm=1&t=busybox_httpd&ulimits=null"
Feb 10 16:17:05 dhcp-41-112.bos.redhat.com docker[4867]: time="2016-02-10T16:17:05.413992484-05:00" level=info msg="GET /v1.20/images/json"
Feb 10 16:17:05 dhcp-41-112.bos.redhat.com docker[4867]: time="2016-02-10T16:17:05.455594651-05:00" level=warning msg="couldn't load b175bcb790231169e232739bd2172bded9669c25104a9b723999c5f366ed7543 from docker.io/busybox:latest: image ID '' is invalid"
Feb 10 16:17:22 dhcp-41-112.bos.redhat.com docker[4867]: time="2016-02-10T16:17:22.906471652-05:00" level=info msg="POST /v1.20/build?cgroupparent=&cpuperiod=0&cpuquota=0&cpusetcpus=&cpusetmems=&cpushares=0&dockerfile=Dockerfile&memory=0&memswap=0&rm=1&t=busybox_httpd&ulimits=null"
Feb 10 16:19:55 dhcp-41-112.bos.redhat.com docker[4867]: time="2016-02-10T16:19:55.898463850-05:00" level=info msg="POST /v1.20/build?cgroupparent=&cpuperiod=0&cpuquota=0&cpusetcpus=&cpusetmems=&cpushares=0&dockerfile=Dockerfile&memory=0&memswap=0&rm=1&t=busybox_httpd&ulimits=null"
I tried a few times, never reproduced it and lost track of my efforts due to other priorities.
I'll give it one more attempt in the next day or so, but it is looking like it is not reproducible.
I tried to reproduce this today on an F23 system using docker-1.10.2-9.git0f5ac89.fc23.x86_64 from Koji, but was unsuccessful.
Closing it as WORKSFORME