Package Details: libpod-docker

Git Clone URL: (read-only)
Package Base: libpod
Description: Use podman as a Docker CLI replacement.
Upstream URL:
Keywords: podman
Licenses: Apache
Conflicts: docker
Provides: docker
Submitter: petris
Maintainer: petris
Last Packager: petris
Votes: 3
Popularity: 1.785036
First Submitted: 2018-10-16 22:13
Last Updated: 2018-11-19 21:23

Required by (74)

Sources (1)

Latest Comments

1 2 Next › Last »

petris commented on 2018-11-19 21:30

@aorth Oops, I'll have to remember that for next time. Thanks!

aorth commented on 2018-11-19 21:27

@petris just by the way, you keep forgetting to reset the pkgrel when updating the pkgver to a new upstream version.

petris commented on 2018-11-09 20:42

@znmeb The libpod-docker is split out for that very reason -- just don't install libpod-docker but install the rest of the libpod packages. The "podman" binary is in the libpod package.

znmeb commented on 2018-11-09 20:41

There seems to be a conflict between Docker and libpod - they can't both be installed:

loading packages...
resolving dependencies...
looking for conflicting packages...
:: libpod-docker and docker are in conflict. Remove docker? [y/N] 

I need to have both installed on my workstation - is this conflict supposed to be there? I just want libpod, not libpod-docker

petris commented on 2018-11-09 20:28

@stratus_ss I looked at the podman man page and it says the default is /var/run/user/$UID/run, however since podman is also reading /etc/containers/storage.conf (which comes from the skopeo package) then that takes precedence. I'd imagine that you might be able to comment out that line to use the podman defaults, or use the --runroot parameter to specify the run directory manually.

stratus_ss commented on 2018-11-07 18:26

@petris I had setup the subuids and gids previously. But thanks for the link. As for the problem with /run, you are correct that seems to have resolved the issue. I didn't do this on my own because it could have been an indication that I missed installing something or there was a step that I missed. I wonder if this should not be taken care of during the package installation to help avoid confusion?

petris commented on 2018-11-06 18:55

@stratus_ss Try creating that directory manually (with appropriate permissions for your user to be able to write to it), and also make sure you setup your subuids and gids:

I believe that's all I needed to do to run rootless.

stratus_ss commented on 2018-11-06 18:14

I seem to be able to run podman as a regular user. I see these errors

container create failed: mkdir /run/runc: permission denied

According to what I have read on Fedora and other systems it should be possible to run containers as non-root users. There is nothing on the Arch wiki for Podman, is there some documentation you know of that can assist?

petris commented on 2018-10-22 20:39

@aorth The package has been updated! Thanks again.

petris commented on 2018-10-22 12:27

@aorth Good point. I’ll make libpod-networking and skopeo required tonight. Thanks again!