bundle command not found when sshing into container

[anthonygreen]

Dockerfile

FROM ruby:latest

RUN apt-get update

RUN apt-get install -y openssh-server
RUN mkdir -p /var/run/sshd

RUN apt-get install -y --no-install-recommends openjdk-7-jdk
RUN apt-get install -y --no-install-recommends subversion

RUN adduser --quiet --disabled-login jenkins
RUN echo "jenkins:password" | chpasswd

RUN mkdir -p /home/jenkins/.subversion
RUN mkdir -p /home/jenkins/.ssl 
RUN mkdir -p /home/jenkins/.ssh

EXPOSE 22

CMD ["/usr/sbin/sshd", "-D"]

when I ssh in bundler is not listed amongst gem list

nor can any bundle command be run

sudo docker run -it --rm ruby:latest bundle --version

does state

Bundler version 1.10.6

though

so maybe some documentation on how it's supposed to work from within the container

[yosifkit]

ssh is scrubbing the environment variables that are setup in the container. Not sure how you would get it to inject them into the resultant shell.

[anthonygreen]

Could be connected to moby/moby#2569

[md5]

I'm not so sure this is specifically related to ssh:

$ diff -u <(docker run --rm ruby gem list) <(docker run --rm ruby sh -c 'adduser --quiet --disabled-login --gecos "" someuser && su - someuser -c "gem list"')
--- /dev/fd/63  2015-08-28 13:19:38.000000000 -0700
+++ /dev/fd/62  2015-08-28 13:19:38.000000000 -0700
@@ -1,5 +1,4 @@
 bigdecimal (1.2.6)
-bundler (1.10.6)
 io-console (0.4.3)
 json (1.8.1)
 minitest (5.4.3)

[md5]

@anthonygreen Which user are you sshing as?

Here's the difference in env between root and a newly added someuser:

$ diff -u <(docker run --rm ruby env) <(docker run --rm ruby sh -c 'adduser --quiet --disabled-login --gecos "" someuser && su - someuser -c env')
--- /dev/fd/63  2015-08-28 13:21:10.000000000 -0700
+++ /dev/fd/62  2015-08-28 13:21:10.000000000 -0700
@@ -1,10 +1,9 @@
-PATH=/usr/local/bundle/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
-HOSTNAME=40dc7f1a125a
-RUBY_MAJOR=2.2
-RUBY_VERSION=2.2.3
-RUBY_DOWNLOAD_SHA256=df795f2f99860745a416092a4004b016ccf77e8b82dec956b120f18bdc71edce
-RUBYGEMS_VERSION=2.4.8
-GEM_HOME=/usr/local/bundle
-BUNDLER_VERSION=1.10.6
-BUNDLE_APP_CONFIG=/usr/local/bundle
-HOME=/root
+SHELL=/bin/bash
+USER=someuser
+MAIL=/var/mail/someuser
+PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
+PWD=/home/someuser
+SHLVL=1
+HOME=/home/someuser
+LOGNAME=someuser
+_=/usr/bin/env

[md5]

I suppose that su - someuser is dropping the surrounding environment as well.

[tianon]

Indeed it is. 😉

[md5]

Just to be clear, the missing GEM_HOME causes this behavior.

[md5]

The missing BUNDLE_APP_CONFIG probably breaks other stuff.

[anthonygreen]

@md5 I'm sshing in as 'jenkins', to diagnose why jenkins can't run bundle in the container when used as a jenkins slave

[md5]

Is Jenkins connecting to the slave via SSH or are you using dynamically provisioned slaves?

[anthonygreen]

@md5 via SSH. It's emerging that in order to get a container based on the official ruby image to work in this manner I will probably need a different approach, since the container is configured as root but the processes are being run as jenkins.

[anthonygreen]

I thought maybe this would work

RUN chown -R jenkins /usr/local

USER jenkins

RUN gem install bundler

USER root

but bundler is still missing from the jenkins user's list of installed gems

[md5]

You'll need to make sure that GEM_HOME=/usr/local/bundle is set (and you should probably set BUNDLE_APP_CONFIG=/usr/local/bundle too).

$ docker run --rm ruby sh -c 'adduser --quiet --disabled-login --gecos "" someuser \
        && su - someuser -c "GEM_HOME=/usr/local/bundle gem list | grep bundler"'