map configs via volumes instead of build new image

[avaika]

Wasn't sure if this will be accepted, thus did the change only for proxy-mariadb and proxy-postgres images. Can do the rest as well, but want to be sure that it won't be just waste of time.

PS. Also added a workaround for #345

[J0WI]

This has already been discussed here: #538 (comment)

@SnowMB could you give more details about this issue and how we can test this?

[J0WI]

🏓 @SnowMB

[SnowMB]

Would love to help in this regard, but I can't. I have no windows machine to test this out. But I can point you to the corresponding issues / commits:

Initial problems came from #104. And I discussed this with @tilosp in #125 (comment)

I don't know if this is still relevant as I see many other images mounting config files, too.

[J0WI]

@tilosp are you fine with dropping the homebrew proxy containers?

[J0WI]

@avaika could you rebase your PR?

[tilosp]

This will not work if the docker client is on a different machine than the docker host.
Because the docker host needs to mount the config files but they are only available on the client machine.
This is for example the case on docker for windows (in Linux container mode). There the client runs under windows and the docker host is a linux vm.

I don't see any other benefits to this pr other than not having to run docker-compose build.
Am i missing something?

So we have to decide whether we want to support remote docker hosts or not.