At the moment the GitHub workflows use the version of Podman that's included in the ubuntu-20.04 virtual environment

Ideally it would be pinned so we could see if an upstream change (either to the Podman API or to the packaging) requires a change here.

The repo2docker tests are hanging. This is reproducible locally as well as in the GitHub workflow:

git clone --depth 1 --single-branch https://github.com/jupyter/repo2docker tests-repo2docker
for d in ./tests-repo2docker/tests/*/; do
  if [ "${d##*tests/}" != "unit/" ]; then
    cp -a $d tests
  fi
done

pytest -vs tests/base

If the repo2docker Dockerfile template is changed, changing /etc/containers/registries.conf shouldn't be necessary for repo2docker/repo2podman, at least:

FROM buildpack-deps:bionic             # short-name
FROM docker.io/buildpack-deps:bionic   # "qulified" name

A few command invocations use "--format", "json", however using docker as the podman_executable requires "--format", "{{json .}}". Manually patching this by switching on the executable value enabled repo2podman to work seamlessly with docker as the CLI.

Currently a no-op

But it should work soon:
containers/buildah#4118

STORY: Users can specify a different engine and arguments to the engine in order to use {podman-remote, nerdctl,} instead of podman.

• podman-remote

  • docs: https://docs.podman.io/en/latest/markdown/podman-remote.1.html
  • docs: https://github.com/containers/podman/blob/main/docs/tutorials/remote_client.md
  • vscode flatpak & podman-remote: https://github.com/flathub/com.visualstudio.code.tool.podman/blob/master/com.visualstudio.code.tool.podman.yml
  • https://www.google.com/search?q=podman+remote

• nerdctl

  • src: https://github.com/containerd/nerdctl

• podman

  • docs: https://docs.podman.io/en/latest/Commands.html
  • docs: https://man.archlinux.org/man/podman.1.en#COMMANDS
  • docs: https://podman.io/docs
  • src: https://github.com/containers/podman