limetech
Container port disabled when editing a container configuration
Why is this field disabled when editing a container? Found myself having to inspect the element and re-enable on multiple occasions. Can't find where this is hidden, otherwise would do a pull request...
Its disabled due to the nasty habit of people not knowing what they are doing changing the container port instead of the host port (or both). Work around is to delete the port and re-add it.
Perhaps those people should learn by trial and error or by reading how Docker works if clear descriptions such as Container Port and Host Port are insufficient and not at the expense of making reconfiguration more difficult or with workarounds for the rest of the user base.
He raises a good point. Maybe put some text in parenthesis aside or underneath the input field:
(this is the port inside the container)
or however you want to word it.
Locking this down removed an entire class of support requests from the forum, as users could no longer change the wrong values. Let's not bring those support requests back :)
If this is opened back up please add a javascript prompt along the lines of "It is very rare that you should have to change the port inside the container, in most cases simply changing the host port is what you want. Are you absolutely sure you want to do this?"
Or follow a pattern and do what is already the way of displaying helpful information for configuration rows in the webGui. Eliminating support requests with configuration limitations and javascript prompts sounds really bad.
Eliminating support requests with configuration limitations and javascript prompts sounds really bad.
Unless you're the one answering the same damn support question over and over and over ;)
I think things should stay as they are. The only persons this affects is developers not end-users of a pre-built template, and as ljm42 stated this removed a ton of support requests on the threads.
Even if it gets switched to a nice huge warning with fireworks, blinking lights, and dancing girls, you're going to get a ton of people thinking that by changing the port they are doing things correctly. And that just increases the workload on the forum.
Unless you're the one answering the same damn support question over and over and over ;)
And that's what tends to particularly annoy everyone who helps out on the threads.
Is the target group people who have no idea what they are doing? Does Portainer for example have configuration lock downs and a ton of questions on their support channels? Is the current limitation implying "you're too stupid to want to change this"?