June 29, 201511 yr At the moment the user is prevented from modifying the container ports when they are defining the container for the first time, however there is nothing stopping the user from editing the container ports once the container has been created. My feature request is to make the container port read only for the user's defined container (my template), as there is no known scenario where editing the container port would be necessary, this would help prevent newbies from incorrectly editing the wrong port side and then wondering why they can't contact the running container. This was discussed with jonp and is possibly a bug, but for now im posting this as an enhancement, text from chat with jonp:- yes def that as well!!, but i think the suggestion justinchase was making was to prevent the user from changing the container port number as defined by the docker template when they are editing, this should then prevent a user from incorrectly modifying the container port and then scratching their head wondering why they cant connect to it. Modify message Ok, yes definitely. That does happen when you are adding a new container with ports defined in the XML template. It appears that when you edit an existing container though, we let folks edit the container port. Probably shouldn't do that. Will discuss with Eric as this may just be a bug.
Archived
This topic is now archived and is closed to further replies.