Provide official Docker image

[angelo-v]

To ease the deployment of NSS on an own server, there should be an official Docker image of NSS on the Docker Hub or any other public registry.

Requirements:

• Provide a production ready Dockerfile
• Automatic build process and publication in a docker registry (e.g. Docker Hub)
• Tagged by version to have full control about the version to run
• Automated tests

As luck would have it, I already prepared a functional, tested Dockerfile of NSS at aveltens/docker-solid-server and run it successfully in production for some months now.

We could move / fork this repository to the Solid organization if you like. Further we need to set up a solid account on Docker Hub and configure the automatic build there.

[michielbdejong]

@Mitzi-Laszlo apparently https://hub.docker.com/u/solid already exists as an org, can you investigate the status of that?

[kjetilk]

@Mitzi-Laszlo, @michielbdejong, @jaxoncreed and I discussed this, and we figured that the best way to do it is probably to have a "Docker Maintainer" role within the Solid project, and since @angelo-v has already done the work, it makes sense if he occupies that role, though I may be pushing the process here. Great if you look into having such a role, and if we could have a suitable home at DockerHub for it.

[angelo-v]

I am willing to maintain an official docker image. But therefore I need access to repository within the solid org as well as solid docker hub account.

[michielbdejong]

I think https://hub.docker.com/u/solid is unrelated to Solid. Maybe we can just pick another name, that's probably easiest and fastest. If we want to try to ask that user to delete their account, then we can also still do that later, and have an alternative Docker hub username in the meantime.

[angelo-v]

Since solidproject is also taken, I just registered solidweb. If someone has a better proposal we could still change, I just wanted to secure one.

[michielbdejong]

@angelo-v so then I think all that's needed to allow you to complete this, is to add you as committer on this github repo, right?

[angelo-v]

We could have a seperate user for the docker image (e.g. a fork of https://github.com/angelo-v/docker-solid-server) or add the docker stuff to a subdirectory within this repo here.
To trigger an automated built add docker hub I need to create and connect a "service user", but I still have to figure out if this is just a regular account or something special.

[Mitzi-Laszlo]

@angelo-v thank you for the contribution!

This conversation is about the project ASAP on Server with Project Manager Jackson Morgan. You can read about all the projects on https://github.com/orgs/solid/projects.

@angelo-v you could either submit a pull request or issue for @jaxoncreed to review as Project Manager. Alternatively you could become a formal Project Contributor and work closely with the Project Manager on the whole project. The admin privileges are a reflection of the role and responsibility. What would you prefer?

@michielbdejong I'll ask around to see who is responsible for https://hub.docker.com/u/solid as well as https://hub.docker.com/u/solidproject and get back to you if I find anything. Meanwhile I'll leave @jaxoncreed as Project Manager to decide if https://hub.docker.com/u/solidweb is the best account to use.

[kjetilk]

Actually, @Mitzi-Laszlo , I think this is broader than the project, we'd want to have Docker images of more than NSS5 at some point. I think this a role closer to the Release Manager than a specific project, though certainly, working with @jaxoncreed is how we'd do it now.

[angelo-v]

I am preferring a dedicated repository within the solid organization, e.g. solid/docker-nss. It would be enough for me to have the permissions for this repository. Just placing a PR here would not be enough, because this does not allow me to setup the docker build. I could do it anyway, but then someone else has to take the "Docker maintainer" role.