Bug 1129770
Summary: | docker build using second form of RUN: invalid environment '' | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Chris Evich <cevich> | ||||
Component: | docker | Assignee: | William Henry <whenry> | ||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | Virtualization Bugs <virt-bugs> | ||||
Severity: | low | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 7.0 | CC: | dwalsh | ||||
Target Milestone: | rc | ||||||
Target Release: | --- | ||||||
Hardware: | x86_64 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2014-10-24 20:14:05 UTC | Type: | Bug | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Chris Evich
2014-08-13 15:36:01 UTC
Created attachment 926498 [details] Context directory + files needed to reproduce Included busybox executable in tarball attachment came from http://www.busybox.net/downloads/binaries/latest/busybox-x86_64 Could this be a problem with pathing? If you fully path all busybox in your example does it work? It's possible, strangely I've seen this problem come and go but have lost track of when/where. We do set up PATH as part of the dockerfile, but I'll double check and give what you suggest a try... ...nope, of course now it's working perfectly for me w/o changing anything :( # rpm -q docker docker-1.2.0-13.el7.x86_64 # docker version Client version: 1.2.0 Client API version: 1.15 Go version (client): go1.3.1 Git commit (client): dc45aa1/1.2.0 OS/Arch (client): linux/amd64 Server version: 1.2.0 Server API version: 1.15 Go version (server): go1.3.1 Git commit (server): dc45aa1/1.2.0 Command: /usr/bin/docker -D build --rm -t buildtest_a0kd_:test /usr/local/autotest/client/tmp/build/src/full Timeout: 120.0 Executed: 1 Duration: 7.32282400131 Exit code: 0 Standard Out: """Step 0 : FROM empty_base_image ---> 6feccfec4d33 Step 1 : MAINTAINER cevich ---> Running in 248e11fd5142 ---> 56279825ed82 Removing intermediate container 248e11fd5142 Step 2 : ADD basic_tree.tar / ---> 80e9ec2f60f1 Removing intermediate container 22352f7505d6 Step 3 : ADD basic_devices.tar / ---> df8ac1a40583 Removing intermediate container a26725469616 Step 4 : ENV PATH /usr/sbin:/usr/bin ---> Running in 88c2f0b032d8 ---> 8eb1fd093ff4 Removing intermediate container 88c2f0b032d8 Step 5 : ADD busybox /usr/sbin/ ---> b30f3fd97e84 Removing intermediate container f5390220f6a7 Step 6 : RUN /usr/sbin/busybox sh -c for item in $(busybox --list-full); do busybox ln -s /usr/sbin/busybox $item; done ---> Running in c9b5d10d0f0a ---> 721b501d2341 Removing intermediate container c9b5d10d0f0a Successfully built 721b501d2341 Standard Error: """ Sending build context to Docker daemon 1.008 MBker daemon 557.1 kB Sending build context to Docker daemon """ I think for now, let's just lower the severity/priority of this BZ until/if we can find a way to more reliably reproduce it in the next few weeks. It's quite possible the underlying problem has been fixed and we can just close. Its been awhile I am going to close. Oh thanks, I forgot about this one. It was happening with a lot more frequency when I opened this, now for sure it's not. I have seen it happen only once or twice since 1.2.0, but still no clue how to repro. it reliably. It's probably just a fluke. |