Package Details: libpod-docker 1.0.0-1

Git Clone URL: https://aur.archlinux.org/libpod.git (read-only)
Package Base: libpod
Description: Use podman as a Docker CLI replacement.
Upstream URL: https://github.com/containers/libpod
Keywords: podman
Licenses: Apache
Conflicts: docker
Provides: docker
Submitter: petris
Maintainer: aorth
Last Packager: aorth
Votes: 6
Popularity: 2.757542
First Submitted: 2018-10-16 22:13
Last Updated: 2019-01-12 09:22

Required by (80)

Sources (1)

Latest Comments

1 2 3 Next › Last »

metalmatze commented on 2019-01-18 17:19

Does this package miss the loopback plugin as dependency in some way or another? I might also miss a step about installing these plugins, but I can't find anything.

aorth commented on 2019-01-12 09:12

@adis hmm, I hadn't used pypodman so I didn't notice that. And on a related note, libpod v1.0.0 moves pypodman out of the main distribution to its own repo.

https://github.com/containers/libpod/commit/45fb935fe44a383ae14f16ab533281687d642c5e

adis commented on 2019-01-11 12:11

There are some missing dependencies, after installation:

$ pypodman ... pkg_resources.DistributionNotFound: The 'humanize' distribution was not found and is required by pypodman

# pacman -S python-humanize

$ pypodman ... pkg_resources.DistributionNotFound: The 'varlink' distribution was not found and is required by podman

(unfortunatelly there is no python-varlink in Arch repos or on AUR.

aorth commented on 2018-12-28 07:31

@jtmb I updated the packaging to resolve the circular dependency by moving the libpod-networking package into libpod.

aorth commented on 2018-12-18 08:45

libpod and libpod-networking seem to have each other as circular dependencies.

@jtmb yes you're right. Actually, I think it's a side effect of the way petris initially packaged libpod, with libpod-networking being optional. Eventually we decided it was better to include networking support by default so it became a hard dependency, but really it should probably just move into the main libpod package base.

jtmb commented on 2018-12-18 08:07

libpod and libpod-networking seem to have each other as circular dependencies.

aorth commented on 2018-12-17 22:49

@silvanoc yes you are exactly right. I just compiled go 1.11.4 from the PKGBUILD and it builds libpod successfully. So once 1.11.4 goes into Arch this package will build again.

silvanoc commented on 2018-12-17 22:01

@aorth you are facing the same regression of Go that I faced yesterday :-)

See here: https://github.com/golang/go/issues/29241

aorth commented on 2018-12-17 21:08

Note: there is something currently broken in go 1.11.3 that causes the libpod build to fail with the following error:

if [ ! -x "/home/aorth/src/git/arch-packages/libpod/src/go/bin/easyffjson" ]; then \
          go get -u github.com/mailru/easyjson/...; \
fi
package github.com/mailru/easyjson/...: github.com/mailru/easyjson/...: invalid import path: malformed import path "github.com/mailru/
easyjson/...": double dot

In my troubleshooting I noticed that the package compiles if I downgrade Arch's go to 1.11.2 from the Arch Rollback Machine. Let's see if the recently release go 1.11.4 will fix it.

petris commented on 2018-12-08 14:48

@aorth You are now the maintainer. Thanks!