We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
podman
Currently, in order to rebuild testdata using podman, make needs to be invoked as follows:
CONTAINER_ENGINE=podman CONTAINER_RUN_ARGS= make
This is a bit verbose and hard to remember. Perhaps the Makefile could run command -v podman and automatically use it when present on the machine?
command -v podman
Also, running rootless containers requires subuids and subgids to be allocated for the current user (see containers/podman#3421 (comment)).
~ cat /etc/subuid /etc/subgid timo:100000:65536 timo:100000:65536
Since I didn't set it up before running podman for the first time, an extra podman system migrate was required to get containers to start properly.
podman system migrate
Ideally, this would be documented as well.
The text was updated successfully, but these errors were encountered:
I can take a stab at this if you like? Should be fairly straightforward.
My only thoughts are what if a user has podman installed, but still wants to use docker?
docker
Sorry, something went wrong.
No branches or pull requests
Currently, in order to rebuild testdata using
podman
, make needs to be invoked as follows:This is a bit verbose and hard to remember. Perhaps the Makefile could run
command -v podman
and automatically use it when present on the machine?Also, running rootless containers requires subuids and subgids to be allocated for the current user (see containers/podman#3421 (comment)).
Since I didn't set it up before running podman for the first time, an extra
podman system migrate
was required to get containers to start properly.Ideally, this would be documented as well.
The text was updated successfully, but these errors were encountered: