Defining a VOLUME in Dockerfile makes it impossible to use as ephemeral/stateless/self-contained image

[patrickfav]

Hi, thanks for the great project, I think homer is the best status/dashboard for self hosted services!

To my issue: I usually try to design docker images as ephemeral/stateless/self-contained where I pack all the necessary files in the image during build time. This makes it easy to:

• Change a file
• Run my docker build (which copies the file to e.g. /www/assets)
• Deploy

Done.

Since the base Dockerfile defines a VOLUME i cant do that because it always wants me to map this volume to somewhere and use that volume instead of the statically copied files. Usually the approach I know of is to NOT define "VOLUME" in dockerfile, but give the user the hint to use it in docker-compose file or docker run, haveing the best of both worlds.

So my question is if you would be open to remove the VOLUME in your Dockerfile?

[bastienwirtz]

Hello @patrickfav,

Thanks for pointing that out. The VOLUME is kind of useless as the content is static, Homer will never make any changes to it. I removed it 👍

[patrickfav]

Awesome, thanks!