Bug: Cmd Truncated in web interface when creating container
Posted: 01 Jul 2021, 20:27
Hello
Some containers do not seem to have their cmd command field properly parsed when editing properties to create a container from an image or edit the properties of an existing image...
Steps to reproduce
1. select official registry =https://registry.hub.docker.com
2. download image boky/postfix (equivalent to github repo bokysan/docker-postfix)
3. create container from image
a. set port such as 10025 for 587
b. add environment variables
ALLOW_EMPTY_SENDER_DOMAINS=true
RELAYHOST=example.com:587
RELAYHOST_USERNAME=nobodycares
RELAYUSER_PASSWORD=something
3. Before applying notice that the command is set to "/bin/sh -c /run.sh" (without quotes)
4. Apply, then note that the container was created but not running
5. If you look at docker.log and go back to the interface you notice that the command is "-c /run.sh"
6. By contrast if using SSH you run sudo docker image inspect boky/postfix, you'll see the correct command.
Some containers do not seem to have their cmd command field properly parsed when editing properties to create a container from an image or edit the properties of an existing image...
Steps to reproduce
1. select official registry =https://registry.hub.docker.com
2. download image boky/postfix (equivalent to github repo bokysan/docker-postfix)
3. create container from image
a. set port such as 10025 for 587
b. add environment variables
ALLOW_EMPTY_SENDER_DOMAINS=true
RELAYHOST=example.com:587
RELAYHOST_USERNAME=nobodycares
RELAYUSER_PASSWORD=something
3. Before applying notice that the command is set to "/bin/sh -c /run.sh" (without quotes)
4. Apply, then note that the container was created but not running
5. If you look at docker.log and go back to the interface you notice that the command is "-c /run.sh"
6. By contrast if using SSH you run sudo docker image inspect boky/postfix, you'll see the correct command.