Skip to content
This repository has been archived by the owner on Jun 11, 2021. It is now read-only.

Starting Jenkins via Kitematic doesn't work #1254

Closed
ilkka opened this issue Nov 26, 2015 · 8 comments
Closed

Starting Jenkins via Kitematic doesn't work #1254

ilkka opened this issue Nov 26, 2015 · 8 comments

Comments

@ilkka
Copy link

ilkka commented Nov 26, 2015

For some reason when starting through Kitematic, the official jenkins image produces a running container, with port mappings and all set up, but no Jenkins process. Starting through normal Docker CLI means works just fine.

@FrenchBen
Copy link
Contributor

Can you share the command you're running via the CLI?

@ilkka
Copy link
Author

ilkka commented Dec 2, 2015

Sure:

$ docker run -d -p 8080 -p 50000 jenkins

@FrenchBen
Copy link
Contributor

That is weird - I don't think we do anything different, but it seems that the CMD is ran, yet the java process is never started.

I'll see if I can pin-point it. Thanks for the issue.

@stoumpos
Copy link

stoumpos commented Dec 4, 2015

Don't know if it is related, but when you start the container from the CLI, the entrypoint is "/bin/tini -- /usr/local/bin/jenkins.sh"; from kitematic, the entry point is "/bin/tini -- /usr/local/bin/jenkins.sh bash".

stoumpos added a commit to stoumpos/kitematic that referenced this issue Dec 4, 2015
If Entrypoint and Cmd are null, then initialize to 'bash'. On all other
cases, when either is null or both are set, we can copy the existing
values without assigning any defaults.
stoumpos added a commit to stoumpos/kitematic that referenced this issue Dec 4, 2015
If Entrypoint and Cmd are null, then initialize to 'bash'. On all other
cases, when either is null or both are set, we can copy the existing
values without assigning any defaults.
stoumpos added a commit to stoumpos/kitematic that referenced this issue Dec 4, 2015
If Entrypoint and Cmd are null, then initialize to 'bash'. On all other
cases, when either is null or both are set, we can copy the existing
values without assigning any defaults.
@FrenchBen
Copy link
Contributor

Yup I think you've nailed it. The extra bash prevents it from running the jenkins, as the script has the followin:

# As argument is not jenkins, assume user want to run his own process, for sample a `bash` shell to explore this image
exec "$@"

I'll checkout your PR, but on first glance it seems like the proper fix. Thanks 👍

@ctran
Copy link

ctran commented Dec 19, 2015

Any update on this?

@FrenchBen
Copy link
Contributor

@ctran we actually pushed a similar fix within the latest cut of Kitematic.
https://github.com/docker/kitematic/blob/master/src/utils/DockerUtil.js#L129

Checkout the latest Docker Toolbox to get the latest version.

@ctran
Copy link

ctran commented Dec 20, 2015

Sweet!!!!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants