#jenkins-community

/

      • olamy joined the channel
      • fredg02 joined the channel
      • https_GK1wmSU joined the channel
      • https_GK1wmSU has left the channel
      • olamy has quit
      • fredg02 has quit
      • https_GK1wmSU joined the channel
      • https_GK1wmSU has left the channel
      • olamy joined the channel
      • jfemia_ joined the channel
      • jfemia has quit
      • olamy has quit
      • olamy joined the channel
      • ogondza joined the channel
      • olamy has quit
      • mpailloncy has quit
      • mpailloncy joined the channel
      • vkotovv joined the channel
      • vkotovv
        rtyler: hey, I'm back again. I saw in the logs that you wanted to tell me something?
      • rtyler: how can I make it work?
      • olamy joined the channel
      • olamy has quit
      • danielbeck
        vkotovv [2017-07-31 18:30:42] <rtyler>their user isn't in the docker group, or at least in the login session, so they couldn't access the docker daemon
      • [2017-07-31 18:30:54] <rtyler>additionally, sudo with this stuff is not likely to work
      • vkotovv has quit
      • vkotovv joined the channel
      • vkotovv
        rtyler: ok, I've added user to docker group and verified that "docker run hello-world" works ok
      • but I still have the same issue (now the same as with sudo): https://gist.github.com/vkotovv/d82ca74f2dc001a...
      • abayer joined the channel
      • zregvart has quit
      • sunshinekitty[m] has quit
      • galactic_hitchhi has quit
      • sunshinekitty[m] joined the channel
      • galactic_hitchhi joined the channel
      • zregvart joined the channel
      • ogondza has quit
      • rtyler
        vkotovv: looking now
      • vkotovv: I have no idea where that image is coming from "source/jenkins.io:latest" that's not what's in scripts/ruby at all
      • ogondza joined the channel
      • ogondza has quit
      • vkotovv
        rtyler: I just used latest revision from the Jenkins.io repo
      • abayer has quit
      • rtyler
        vkotovv: I there's no "source/jenkins.io" anywhere in the tree, so I'm not sure what's happening there
      • vkotovv
        rtyler: I've debugged ./scripts/ruby, here is what gets executed:
      • + exec docker run --rm -u 1000:1000 -e LANG=C.UTF-8 -e HOME=/home/vadim/work/open source/jenkins.io -e 'GEM_HOME=/home/vadim/work/open source/jenkins.io/vendor/gems' -e 'BUNDLE_PATH=/home/vadim/work/open source/jenkins.io/vendor/gems' -e 'BUNDLE_APP_CONFIG=/home/vadim/work/open source/jenkins.io/vendor/gems/.bundle' -e BUNDLE_DISABLE_SHARED_GEMS=true -v /home/vadim/work/open source/jenkins.io:/home/vadim/work/open source/jenkins.io:delegated -w
      • /home/vadim/work/open source/jenkins.io ruby:2.3 bundle install --path=vendor/gems
      • Unable to find image 'source/jenkins.io:latest' locally
      • docker: Error response from daemon: repository source/jenkins.io not found: does not exist or no pull access.
      • rtyler
        aha!
      • vkotovv
        please take a look at ./scripts/ruby
      • rtyler
        it's the space in your path
      • vkotovv
        as usual :/
      • rtyler
        vkotovv: perhaps quote "${PWD}" in those scripts
      • I never have spaces in my paths, so I didn't notice this issue
      • good bug catching :D
      • vkotovv
        no luck
      • the result is the same
      • + exec docker run --rm -u 1000:1000 -e LANG=C.UTF-8 -e HOME=/home/vadim/work/open source/jenkins.io -e 'GEM_HOME=/home/vadim/work/open source/jenkins.io/vendor/gems' -e 'BUNDLE_PATH=/home/vadim/work/open source/jenkins.io/vendor/gems' -e 'BUNDLE_APP_CONFIG=/home/vadim/work/open source/jenkins.io/vendor/gems/.bundle' -e BUNDLE_DISABLE_SHARED_GEMS=true -v '/home/vadim/work/open source/jenkins.io:/home/vadim/work/open source/jenkins.io:delegated' -w
      • '/home/vadim/work/open source/jenkins.io' ruby:2.3 bundle install --path=vendor/gems
      • Unable to find image 'source/jenkins.io:latest' locally
      • docker: Error response from daemon: repository source/jenkins.io not found: does not exist or no pull access.
      • rtyler: I think I will debug it a bit more tomorrow and try to prepare a PR
      • rtyler
        vkotovv: I'm digging around, docker is having trouble with the -v argument having a space in it
      • I'm not sure what the best way to escape that is
      • I'll poke a bit after I fix something else, and maybe i'll fix it before you wake up :D
      • vkotovv
        sounds good :D
      • see you
      • vkotovv has quit
      • abayer joined the channel
      • abayer has quit
      • ogondza joined the channel
      • fredg02 joined the channel
      • mpailloncy has quit
      • abayer joined the channel
      • ogondza has quit
      • abayer has quit
      • olamy joined the channel
      • jenkins-io
        [13jenkins.io] 15rtyler opened pull request #1049: Handle properly invoking docker containers when the tree has a file path with spaces (06master...06spaceghost-coast-to-coast) 02https://github.com/jenkins-infra/jenkins.io/p...
      • olamy has quit