docker-idrac6: cannot start
I apologize if my question seems dumb.
I have installed Docker Desktop for Mac, then run the said command with relevant parameters (IDRAC_HOST is an IP address of a remote server):
docker run -d -p 5800:5800 -p 5900:5900 -e IDRAC_HOST=https://123.123.123.123 -e IDRAC_USER=root -e IDRAC_PASSWORD=1234 domistyle/idrac6
Running docker container ls shows the container running, but it shuts down after a few seconds:
$ docker container ls
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
b0437b539c82 domistyle/idrac6 "/init" 4 seconds ago Up 2 seconds 0.0.0.0:5800->5800/tcp, 0.0.0.0:5900->5900/tcp sad_goldstine
$ docker container ls
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
b0437b539c82 domistyle/idrac6 "/init" 6 seconds ago Up 5 seconds 0.0.0.0:5800->5800/tcp, 0.0.0.0:5900->5900/tcp sad_goldstine
$ docker container ls
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
b0437b539c82 domistyle/idrac6 "/init" 8 seconds ago Up 6 seconds 0.0.0.0:5800->5800/tcp, 0.0.0.0:5900->5900/tcp sad_goldstine
$ docker container ls
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
Is this the intended behavior? How to I debug this? I’ve tried to connect to the instance, but the time is too short for that.
Please send some help as I’d really love to use this instead of a VM with Windows…
About this issue
- Original URL
- State: open
- Created 5 years ago
- Comments: 35 (6 by maintainers)
I’ve managed to solve this in a bit of a simpler way - I think. The IDRAC self-signed certificate is not accepted by modern OSes and the ‘no-check-certificates’ on the wget calls in startapp.sh doesn’t bypass this. If you manually try to download the jar files from your IDRAC in the browser, you’ll be able to accept the certificate and get the files but via the startapp script there’s no easy way to do this. The IDRAC6 also has weak key which is not trusted by modern versions of openssl either. If you try to do wget the file from a terminal you will see these errors.
You could probably set up your docker container to reduce the security levels for openssl within the container but I didn’t bother - instead, I just used a browser to download the files from the IDRAC and place them in the docker host’s working app folder (the location they would be downloaded to via the script). This is trivial to setup if you use the provided docker-compose file. With the (3) .jar files in place, the container spun up just fine and the IDRAC was accessible flawlessly.
The files can be seen in the startapp.sh file but for reference they can be downloaded via your browser here:
Hope this helps!
@SirThunder88 the steps in last comment check out the code to your home directory. If you have setup a SSH key with git pick the first one, if not use the second one, and finally if you don’t have git installed on the CLI you download the archive.
I am running an Ubuntu VM and just installed it natively. I then loaded the iDRAC web interface and clicked the connect button which downloaded the
jnlpfile. Inside that file I edited theusernameandpasswordto be the actualusernameandpasswordnot the temporary one it uses by default. I repeated this process for all my servers. When I want to connect a specific one I just click thejnlpfor that server. Doesn’t isn’t used / required at all for this as I could not get the container to work.