JENKINS-30200: Nullpointer exception while connecting to a docker

[djaara]

container

Looks like due to Docker API changes between v1.19 and v1.20
create container call should contain ExposedPorts instead of
PortSpecs. Change was tested with Docker 1.8.2 and 1.7.1.

[KostyaSha]

What image did you use for testing?

[djaara]

I've used my own docker image, created following steps listed on Docker Plugin. Used docker image should not have nay impact IMO.

Here is dockerfile I've used for my image:

FROM ubuntu:latest
MAINTAINER "Jaroslav Barton" <jbarton@example.com>
RUN apt-get clean; \
  apt-get update -y; \
  apt-get upgrade -y; \
  apt-get install -y libdevmapper1.02.1 curl unzip openjdk-7-jdk git maven openssh-server curl wget; \
  apt-get clean; \
  rm -rf /var/lib/apt/lists/*; \
  ln -s /lib/x86_64-linux-gnu/libc.so.6 /lib64/libc.so.6; \
  ln -s /lib/x86_64-linux-gnu/libdevmapper.so.1.02.1 /lib/x86_64-linux-gnu/libdevmapper.so.1.02; \
  useradd -ms /bin/bash jenkins; \
  echo jenkins:jenkins | chpasswd; \
  mkdir /root/.m2; \
  mkdir /var/run/sshd
ENV JAVA_HOME /usr/lib/jvm/java-7-openjdk-amd64
COPY settings.xml /root/.m2/settings.xml

[KostyaSha]

Used docker image should not have nay impact IMO.

This is the main problem, image should have EXPOSE place, that's why https://github.com/jenkinsci/docker-plugin/blob/master/CONTRIBUTING.md as the first step asks to use verified image. Also old launching code was hardcoded to expect EXPOSE 22, that i probably unhardcoded. Without integration tests i don't want change behaviour now.

Relates to #309

[djaara]

I see. Thank you for few more links.

[KostyaSha]

@djaara feel free to investigate and provide results :) I think the same issue will be if somebody wants expose additional port in template. I hope wrote integration tests soon so it will be possible to play with changes.

[KostyaSha]

retriggering pr for user on IRC. Surprised that @magnayn not merged all PRs yet.

[KostyaSha]

It was sarcasm ;)