Starting Jenkins via Kitematic doesn't work #1254
Comments
Can you share the command you're running via the CLI? |
Sure:
|
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. |
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". |
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.
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.
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.
Yup I think you've nailed it. The extra bash prevents it from running the jenkins, as the script has the followin:
I'll checkout your PR, but on first glance it seems like the proper fix. Thanks 👍 |
Any update on this? |
@ctran we actually pushed a similar fix within the latest cut of Kitematic. Checkout the latest Docker Toolbox to get the latest version. |
Sweet!!!! |
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.
The text was updated successfully, but these errors were encountered: