[Jenkins-infra] Weirdness on celery vs cabbage

Andrew Bayer andrew.bayer at gmail.com
Wed Jan 20 23:24:24 UTC 2016


docker exec $(docker run -t -d -u 1003:1003 -u root -w
/home/jenkins/slave/workspace/tmp-jenkins-20-jenkinsfile/packaging -v
/home/jenkins/slave/workspace/tmp-jenkins-20-jenkinsfile/packaging:/home/jenkins/slave/workspace/tmp-jenkins-20-jenkinsfile/packaging:rw
jenkins-packaging-builder:0.1 sleep 30) cat /etc/hostname

rather - sorry, pasted in the result too.

On Wed, Jan 20, 2016 at 3:24 PM, Andrew Bayer <andrew.bayer at gmail.com>
wrote:

> So here's a way to reproduce it - run this command on both cabbage and
> celery and see how the output differs - it should be a docker container ID,
> but on celery, it's...celery.
>
> docker exec $(docker run -t -d -u 1003:1003 -u root -w
> /home/jenkins/slave/workspace/tmp-jenkins-20-jenkinsfile/packaging -v
> /home/jenkins/slave/workspace/tmp-jenkins-20-jenkinsfile/packaging:/home/jenkins/slave/workspace/tmp-jenkins-20-jenkinsfile/packaging:rw
> jenkins-packaging-builder:0.1 sleep 30) cat /etc/hostname
> bfe25d537823
>
> A.
>
> On Wed, Jan 20, 2016 at 2:18 PM, Andrew Bayer <andrew.bayer at gmail.com>
> wrote:
>
>> https://ci.jenkins-ci.org/job/tmp-jenkins-20-jenkinsfile/24/console -
>> fails on celery, works on cabbage, and for that matter, works from the
>> commandline on celery. I've seen this whether doing 'sh "docker run ..."'
>> or docker.image.inside, I've nuked the image and rebuilt it, and...I have
>> no idea what's going on. Anyone have any ideas?
>>
>> A.
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.jenkins-ci.org/pipermail/jenkins-infra/attachments/20160120/4a3b1738/attachment.html>


More information about the Jenkins-infra mailing list