RFE: Updated base OCI images and Dockerfiles

Deliver a canonical Docker base image(s)

Currently, the PyPi package (pip install tahoe-lafs) is the most popular option. In some cases, it would be useful to have a current docker (OCI) image, along with the code used to build it (Dockerfile).

At the 2024-06-18 meeting, @meejah , @hacklschorsch , @btlogy , ccx and cypher agreed that we should include a description of the targeted purpose of the images and any limitations or caveats.

For example, we may decide to have something like:

• Tahoe-LAFS:base (essentially the PyPi package, ubuntu LTS)
• Tahoe-LAFS:distroless (based on wolfi, or other distroless base)
• Tahoe-LAFS:server (a node ready for cloud deployment)

Use gitlab CI for pushing images to gitlab registry

Naming convention for images:

Now:

registry.gitlab.com/highly-unlikely/tahoe-dx-prime/tahoe-lafs-base:latest
registry.gitlab.com/highly-unlikely/tahoe-dx-prime/tahoe-lafs-distroless:latest

Later:

registry.gitlab.com/highly-unlikely/tahoe-dx-prime/tahoe-lafs-base:latest
registry.gitlab.com/highly-unlikely/tahoe-dx-prime/tahoe-lafs-distroless:latest
registry.gitlab.com/highly-unlikely/tahoe-dx-prime/tahoe-lafs-dev:latest

Where dev is the all-in-one setup for sample apps or new developers.

Multi arch builds

Create issues for each

• amd64
• ARM (hf? AARCH64?)
• Apple Silicon?