I realized I made a simple mistake after spending 30 minutes trying to figure out why the DTYPE environment variable wasn't working in Docker. The command line option is --dtype, so I thought I was doing something wrong. However, it turns out the correct environment variable name is DATATYPE in Docker, and I learned this the hard way by not checking the entrypoint.sh file earlier.
What is the best solution then? Ideally, each command line option would have a corresponding environment variable with a consistent name. Given that users can provide conflicting configurations through environment variables and command line options, the latter should take priority. Even better, we could manage all settings in a configuration file, which could be loaded either through a --config-file command line option or a CONFIG-FILE environment variable that specifies the file path.
Below is a proposed format for the configuration file:
š The feature, motivation and pitch
I realized I made a simple mistake after spending 30 minutes trying to figure out why the
DTYPE
environment variable wasn't working in Docker. The command line option is--dtype
, so I thought I was doing something wrong. However, it turns out the correct environment variable name isDATATYPE
in Docker, and I learned this the hard way by not checking theentrypoint.sh
file earlier.What is the best solution then? Ideally, each command line option would have a corresponding environment variable with a consistent name. Given that users can provide conflicting configurations through environment variables and command line options, the latter should take priority. Even better, we could manage all settings in a configuration file, which could be loaded either through a
--config-file
command line option or aCONFIG-FILE
environment variable that specifies the file path.Below is a proposed format for the configuration file:
Thank you!
Alternatives
No response
Additional context
No response