Hello everyone, I have a question about the envs section in the container as follows:
The key in evns is the same and will cause an error! But value is different. I don’t know if there is a way to add value in the same key? If I let the key be some random name and then I paste the value I intend to be the key later, is that okay?
There is no sense to have same key (env. variable name) under same config name.
If you need to have same env. variable (key) with different value on different containers then create it with different name.
/container/envs/add name=container1_envs key=SOME_ENV value="value1"
/container/envs/add name=container2_envs key=SOME_ENV value="value2"
Unfortunately I’m trying to run on a container!
To run same container to have for same variable different value? Can you specify case? You can set value before running container if you want in some case to have different value. Using scripts it is possible to automate staring container with different env. var. values…
If I run the command line will it show the same error as the gui operation? Some dockers will have different data but the variable names are the same!
dockers - plural. Then I think you misunderstood my post #2.
Create same env. variable (key) with different value and config name (I have some also for different containers), assign on each container env. config with name that contains that same env. variable with desired value.
So the envlist section can add commas in that entry? For example: container 1, container 2
No afaik, env. list can have multiple variables, create env. list per container and assign on each variables that are needed, even duplicates, eg:
/container/envs/add name=container1_envs key=SOME_ENV_1 value="env_1_value1"
/container/envs/add name=container1_envs key=SOME_ENV_2 value="env_2_value1"
/container/envs/add name=container2_envs key=SOME_ENV_1 value="env_1_value1"
/container/envs/add name=container2_envs key=SOME_ENV_2 value="env_2_value2"
for container1 and container2 - SOME_ENV_1 will have same value, but SOME_ENV_2 different.
Isn’t it necessary to stick to container 1? Because the container has some variations, it’s still okay to just differ in value? What happens when a new container is added? For example: the variable name is parical but the value will be as follows:
- 53/53 tcp
- 53/53 udp
Can you explain to me how to handle this part?
It all depends if you have same or different values for same variable names. Env. lists are lists of variables with unique keys (env. variable name in containers), if you have container that have ALL same variables and its values like in other container list can be reused, if not, create new list with all needed variables and as mentioned above even if is same that is in other list since you cannot combine lists for same container.
Is there no way to paste multiple values for a key?
If application that reads variable process its value with some separator - yes, but that is application level of value reading, system shell supports variable=value, value is list of characters…