This is needed because when updating an existing environment, the
existing volume will shadow away the changes done on container build.

For some reason inobvious to me, the original default.conf happened
ending up in the image from time to time.

Eases deployment, especially on hosters that charge per volume.