Running with environment variables does not seem to be working #10
Description
I might be missing something but I can't get the container to work with environment variables.
So, the log output is like so:
[email protected] | All required settings passed as environment variables. Skipping config file creation.
[email protected] | Started runsvdir, PID is 14. Waiting for processes to start....
[email protected] | All required settings passed as environment variables. Skipping config file creation.
[email protected] | Started runsvdir, PID is 14. Waiting for processes to start....
[email protected] | [Sep 12 21:17:08] Launching the noip2 daemon
[email protected] | [Sep 12 21:13:44] Launching the noip2 daemon
[email protected] | Can't locate configuration file /config/no-ip2.generated.conf. (Try -c). Ending!
[email protected] | Can't locate configuration file /config/no-ip2.generated.conf. (Try -c). Ending!
[email protected] |
[email protected] |
[email protected] | run: noip: (pid 17) 5s
[email protected] | run: noip: (pid 17) 5s
[email protected] | [Sep 12 21:13:49] Current status
[email protected] | [Sep 12 21:17:13] Current status
[email protected] | Can't locate configuration file /config/no-ip2.generated.conf. (Try -c). Ending!
[email protected] | [Sep 12 21:13:49] ERROR: noip2 daemon has stopped running. Restarting it in 60 seconds.
[email protected] | Can't locate configuration file /config/no-ip2.generated.conf. (Try -c). Ending!
So the environment variables are found, and is passing the checks.
This then causes config file generation to be skipped (parse_config_file.sh)
Well and good, BUT, looking at noip.sh, it used GENERATED_CONFIG_FILE=/config/no-ip2.generated.conf for the configuration file location, which is passed to the noip2 executable via -c parameter.
And that file does not exist, because it's creation was skipped, because the env vars were passed.
So noip client dies, gets started again , rinse, repeat.
Did I miss something here? Am I doing something wrong?