-
Notifications
You must be signed in to change notification settings - Fork 410
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
New docker containers always use the default app.config #742
Comments
@nilsnolde I'm not entirely sure this fixes the issue. The custom configuration is only copied when |
How this is implemented now only works when you build the image yourself, and even then there is some code to scrub out all profiles except for "car". This can easily be integrated to work with custom |
Something like this, or add this argument to docker run:
|
See #772 |
It's very annoying: whenever a new container is created (e.g. when just changing some env var in
docker-compose.yml
) the new container reads the defaultapp.config
provided by the image. Regardless if the user actually has a valid config in./ors-conf
.Not hard to remedy:
The problem is that
mvn package
is run in the image itself, which packages the defaultapp.config
into the WAR file. So currently there's no way to access theapp.config
Tomcat will use since it's inside the WAR.The lines
need to be in
docker-entrypoint.sh
, not in theDockerfile
, with some logic so we don't package needlessly if nothing changed.The text was updated successfully, but these errors were encountered: