1

How do I open a training ticket?

Josh Bernardini

August 28, 2020 19:53

None

Follow

The Install Lab Environment:Troubleshooting says, "If you still cannot use the lab environment, depending on your training type:'Self Paced': please open a ticket by following the instructions found in the 'Open a training ticket' at the start of the course." But I can't find "Open a training ticket." 

 

I see several people here have reported the same issue without resolution: I can't access the Lab Home Page because not all of the containers are starting.

 

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
fbe2ecafdb28 cloudbees/training-jenkins-agent:jdk7-master-b8c2e2dd2abc7edf474f2e75aa95d28f0154bd65 "/sbin/tini -g -- ba…" 2 minutes ago Up About a minute 22/tcp, 2375-2376/tcp jdk7-ssh-agent
e3a015e07ff1 verb/socat:alpine "/usr/bin/socat tcp-…" 2 minutes ago Up About a minute 2375/tcp docker_docker-service_1_b3a61dd506e1
16bf30011234 cloudbees/training-devbox:master-b8c2e2dd2abc7edf474f2e75aa95d28f0154bd65 "/sbin/tini -g -- ba…" 2 minutes ago Up About a minute 2375-2376/tcp, 7681/tcp devbox

• Facebook
• Twitter
• LinkedIn

3 comments

• 0
  
  Josh Bernardini August 28, 2020 20:02

  Looks like I'm getting one additional container up with every vagrant halt/up cycle.
  
  CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
  dbd6a938b241 cloudbees/training-jenkins-agent:jdk7-master-b8c2e2dd2abc7edf474f2e75aa95d28f0154bd65 "/sbin/tini -g -- ba…" 16 seconds ago Up 292 years jdk7-ssh-agent
  25445f342fee cloudbees/training-jenkins-agent:jdk8-master-b8c2e2dd2abc7edf474f2e75aa95d28f0154bd65 "/sbin/tini -g -- ba…" 17 seconds ago Up 14 seconds 22/tcp, 2375-2376/tcp jdk8-ssh-agent
  fb6b694c5726 cloudbees/training-devbox:master-b8c2e2dd2abc7edf474f2e75aa95d28f0154bd65 "/sbin/tini -g -- ba…" 17 seconds ago Restarting (137) 9 seconds ago 2375-2376/tcp, 7681/tcp devbox
  3e4cfb47b485 postgres:10-alpine "docker-entrypoint.s…" 17 seconds ago Up 16 seconds (healthy) 5432/tcp gitserver-db
  085a9d33dd91 verb/socat:alpine "/usr/bin/socat tcp-…" 17 seconds ago Up 16 seconds 2375/tcp docker_docker-service_1_b3a61dd506e1
  628cdcc87d1a cloudbees/training-jenkins:lts-master-b8c2e2dd2abc7edf474f2e75aa95d28f0154bd65 "/sbin/tini -- bash …" About a minute ago Up 18 seconds (health: starting) 8080/tcp, 50000/tcp jenkins

• 0
  
  Josh Bernardini August 28, 2020 20:42

  I got all or most of them up after a series of reboots and then service docker restart brought them all up so that looks like its probably what you wanna do. But now it looks like the jenkins container is not listening on the expected ports? 50,000 instead of 5000? And the ports are not published?

  628cdcc87d1a cloudbees/training-jenkins:lts-master-b8c2e2dd2abc7edf474f2e75aa95d28f0154bd65 "/sbin/tini -- bash …" 27 minutes ago Up 13 minutes (healthy) 8080/tcp, 50000/tcp jenkins

   

  cloudbees-lab:~$ docker port jenkins
  cloudbees-lab:~$ docker port jenkins 8080
  Error: No public port '8080/tcp' published for jenkins
  cloudbees-lab:~$ docker port jenkins 50000
  Error: No public port '50000/tcp' published for jenkins

• 0
  
  Josh Bernardini August 28, 2020 20:44

  ah I see from someone else's screenshot I'm still missing one container called 'front' that has port 5000 published.