Push devcontainer to new Docker Hub repository

[tschaffter]

Configure VS Code devcontainer to use the new image ghcr.io/sage-bionetworks/challenge-devcontainer:latest.

[tschaffter]

@zaro0508 @xschildw I would like to set the visibility of the Docker image ghcr.io/sage-bionetworks/challenge-devcontainer created by this repo to Public. However, I don't have the required permission to change the visibility of this image:

The definition of this image lives here.

Until now we pushed this image to Docker Hub but I wanted to give a try to ghcr.io for the first time.

I have a few questions:

• Does Sage supports / promotes using ghcr.io?
• If yes, can you please change the visibility of this image to Public? This will make the development workflow used by our team smoother.

[tschaffter]

From the Confluence page Building Container Images:

GitHub Container Registry (ghcr)

Building a container and pushing it to ghcr requires a service account within the GitHub organization. This service account must be an owner of the organization. When a container repository is first created on ghcr it is private. To make it public, you must log in with the service account and manually make the package visibility public.

The credentials for this service account are kept in LastPass and are made available only to other owners of the organization because the service account has excessive permissions.

Hosting the image on ghcr is accepted at Sage according to the doc.

@zaro0508 @xschildw Could one of you make the above ghcr image publicly available?

[tschaffter]

EDIT: After thinking about it, it's easier for our team to continue using Docker Hub instead of ghcr because I already have the required permission to push to Docker Hub.

[tschaffter]

Giving it a try!