Historically farmOS had only published amd64 docker images, so FarmData2 included its own build of farmOS as an arm64 image. Not that farmOS publishes an official arm64 image we should move to using it.
FarmData2 should still produce and publish its own farmOS images, but it should do it FROM the official farmOS images instead of building from the source. This will be similar to what is done for postgres, where we just make our own version of their image. The FarmData2 image of farmOS should be built using the 3.x-dev image. That image will move as farmOS builds toward its next release, but the FarmData2 version will only move when we decide to update our image. This provides us with greater stability and control in our dev enviornment.
With farmOS however, there will still be a few things that we need to customize. The README file in the farmos3 directory provides information about how the image will need to be customized.
Historically farmOS had only published amd64 docker images, so FarmData2 included its own build of farmOS as an arm64 image. Not that farmOS publishes an official arm64 image we should move to using it.
The farmOS images can be found here: https://hub.docker.com/r/farmos/farmos/tags
FarmData2 should still produce and publish its own farmOS images, but it should do it
FROMthe official farmOS images instead of building from the source. This will be similar to what is done for postgres, where we just make our own version of their image. The FarmData2 image of farmOS should be built using the3.x-devimage. That image will move as farmOS builds toward its next release, but the FarmData2 version will only move when we decide to update our image. This provides us with greater stability and control in our dev enviornment.With farmOS however, there will still be a few things that we need to customize. The
READMEfile in the farmos3 directory provides information about how the image will need to be customized.