Track releases in upstream OVM

[breznak]

I'd like to use this docker image for OMV, I have a question about up-to-date status of the OVM installed (seeing this repo has lates update some ~5mo ago)?

I'd like to stay synced with the upstream:
https://github.com/openmediavault/openmediavault/branches
either on the stable (currently 3.x branch), or the devel (master).

Is it necessary to somehow synchronize in this repo, or is an update from within the image enough? If the image is ephemeral (like eg https://github.com/kylemanna/docker-openvpn ) then the updates must be synced to the image file here, and clients update only using docker pull ...

[ikogan]

The image is ephemeral, I would recommend setting up a Dockerfile that updates the repository and building your own image. Feel free to submit a PR and I'll add a tag for the 3.x and devel branches.

[breznak]

This will mean to:

• update OMV sources: https://github.com/ikogan/docker-openmediavault/blob/master/openmediavault.list#L1
• update (now obsoleted) Debian base: https://github.com/ikogan/docker-openmediavault/blob/master/Dockerfile#L1

[edrex]

It looks like @OIK2 updated to Erasmus master...OIK2:master

I will try to do a build when I'm at my laptop next. update: i was considering deploying omv as a docker container, but changed my mind, so no build from me.

[OIK2]

My fork also changes the base OS to Raspbian, to make it Raspberry Pi compatible. I have not had the opportunity to test it just yet, so I can only wish you luck, and see what I can do about any issues that arise.