i rebuild the UI docker container for edge use because we needed ARM32 support & remote access.
I need some info on whether to push this as contribution. @stefan.feilmeier, hope you can help me with that.
the new build changes the following:
moved to alpine:3 base images (smaller). no more s6 overlays, but chown-at-build. ARM32 now supported
NGINX reverse proxy setup to support remote access to the UI. No need for the backend setup to view a remote UI now when the right environment vars are enabled.
because these changes are quite extensive i don’t want to just push then.
where can i post this (the dockerfile & reverse proxy setup) for a pre-review as i dont think just pushing this as PR is too much.
ARM32 support would definitely be useful, especially for edge deployments. I have already played with the idea.
i would not completely remove the s6 overlay builds as they make debugging way easier, as they can keep the container alive when the services crashes.
Maybe it could make sense to keep the current images for the default builds and offer your Alpine-based variant as a separate “-slim” image.
In any case, I am curious to see what you built. It might actually be easiest if you open a PR on GitHub so we can review the changes and discuss them there.
