-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dockerfile does not build #12
Comments
@mcatanzaro can you try again with the Dockerfile there now? |
I see I need to edit the Dockerfile now:
But how do I set the port to use? I guess that obsoletes /etc/azafea-metrics/proxy/config.toml? Then the installation instructions will need to be updated accordingly? |
@mcatanzaro you don't need to edit the Dockerfile, instead you have 2 options. You can either create a configuration file and run just like the documentation instructs. Alternatively, you can use environment variables and forgo the configuration file like so:
The 2nd option uses a configuration file that is generated from the environment variables you set when running the image (no need to rebuild the image). |
OK, I understand now. It contains the placeholder REDIS_HOST and REDIS_PASSWORD variables set to localhost and "CHANGE ME!!", which strongly suggests that they should be changed. But when following the installation instructions, they should be ignored and not changed. It's very confusing tbh to have 'change me' variables in the Dockerfile that are supposed to be ignored and not changed when following the instructions.
I understand that, if I wanted to follow your second configuration option, instead of following the instructions, then it would not be possible to use a redis instance on a non-default port, because you provide REDIS_HOST and REDIS_PASSWORD environment variables, but not a REDIS_PORT variable. The sample configuration file in the installation instructions does not have this problem. |
I tested the new Dockerfile but it really doesn't work when following the installation instructions. Using my modified Dockerfile from my first post,
But with your new Dockerfile, the same command fails:
|
Note that your new Dockerfile in endlessm/azafea#103 does NOT have this problem. That one works fine. (I was expecting them both to fail in the same way.) |
@mcatanzaro instead of running the container with the command |
Yes, that works. Will update my PR in #13. |
This is a companion issue to endlessm/azafea#103. The azafea-metrics-proxy Dockerfile does not build. The following are the minimal changes I required to get a successful build (using docker rather than podman):
The text was updated successfully, but these errors were encountered: