Jump to content

Field in Docker Container Advanced View settings for Post Repository Params


jedimstr

Recommended Posts

Currently the webUI Docker Container Advanced View has a field for entering Extra Parameters, but those are for Docker parameters in the run command before the Repository listing.  Many containers have a need for container specific parameters after the Repository listing in the run command.  You can add the parameters in the Repository listing itself, but according to the Fix Common Problems plugin this is deprecated ...

 

Adding extra parameters by including them in the repository (eg: --cpuset-cpus) is deprecated, and may impact the ability of dockerMan to correctly manage your application (eg: unable to update, etc). The proper way to add extra parameters is through the Extra Parameters section when you edit the container

 

As mentioned, using Extra Parameters places those parameters before the Repository, so isn't applicable to container specific parameters like what is needed for cadvisor

 

Example Repository field for cadvisor

google/cadvisor:latest -storage_driver=influxdb -storage_driver_host=tower:8086

 

Having an Advanced View field specifically for this use would be a cleaner way to do it.

Link to comment

Currently the webUI Docker Container Advanced View has a field for entering Extra Parameters, but those are for Docker parameters in the run command before the Repository listing.  Many containers have a need for container specific parameters after the Repository listing in the run command.  You can add the parameters in the Repository listing itself, but according to the Fix Common Problems plugin this is deprecated ...

 

Adding extra parameters by including them in the repository (eg: --cpuset-cpus) is deprecated, and may impact the ability of dockerMan to correctly manage your application (eg: unable to update, etc). The proper way to add extra parameters is through the Extra Parameters section when you edit the container

 

As mentioned, using Extra Parameters places those parameters before the Repository, so isn't applicable to container specific parameters like what is needed for cadvisor

 

Example Repository field for cadvisor

google/cadvisor:latest -storage_driver=influxdb -storage_driver_host=tower:8086

 

Having an Advanced View field specifically for this use would be a cleaner way to do it.

FCP isn't the end all, be all error detection, and as noted there is a valid way reasons to do this.  However, as it currently stands, adding parameters into the repository section messes up other actions of the GUI (container updates).  Another section would solve some more problems
Link to comment
  • 3 months later...

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...