conda-forge / podman-feedstock

A conda-smithy repository for podman.

About podman-feedstock

Feedstock license: BSD-3-Clause

Home: https://podman.io/

Package license: Apache-2.0

Summary: Podman: A tool for managing OCI containers and pods.

Development: https://github.com/containers/podman

Documentation: https://docs.podman.io/en/latest/

Podman (the POD MANager) is a tool for managing containers and images, volumes mounted into those containers, and pods made from groups of containers. Podman is based on libpod, a library for container lifecycle management that is also contained in this repository. The libpod library provides APIs for managing containers, pods, container images, and volumes.

Current build status

Azure

Variant Status linux_64

Current release info

Name	Downloads	Version	Platforms

Installing podman

Installing podman from the conda-forge channel can be achieved by adding conda-forge to your channels with:

conda config --add channels conda-forge
conda config --set channel_priority strict

Once the conda-forge channel has been enabled, podman can be installed with conda:

conda install podman

or with mamba:

mamba install podman

It is possible to list all of the versions of podman available on your platform with conda:

conda search podman --channel conda-forge

or with mamba:

mamba search podman --channel conda-forge

Alternatively, mamba repoquery may provide more information:

# Search all versions available on your platform:
mamba repoquery search podman --channel conda-forge

# List packages depending on `podman`:
mamba repoquery whoneeds podman --channel conda-forge

# List dependencies of `podman`:
mamba repoquery depends podman --channel conda-forge

About conda-forge

conda-forge is a community-led conda channel of installable packages. In order to provide high-quality builds, the process has been automated into the conda-forge GitHub organization. The conda-forge organization contains one repository for each of the installable packages. Such a repository is known as a feedstock.

A feedstock is made up of a conda recipe (the instructions on what and how to build the package) and the necessary configurations for automatic building using freely available continuous integration services. Thanks to the awesome service provided by Azure, GitHub, CircleCI, AppVeyor, Drone, and TravisCI it is possible to build and upload installable packages to the conda-forge anaconda.org channel for Linux, Windows and OSX respectively.

To manage the continuous integration and simplify feedstock maintenance conda-smithy has been developed. Using the conda-forge.yml within this repository, it is possible to re-render all of this feedstock's supporting files (e.g. the CI configuration files) with conda smithy rerender.

For more information please check the conda-forge documentation.

Terminology

feedstock - the conda recipe (raw material), supporting scripts and CI configuration.

conda-smithy - the tool which helps orchestrate the feedstock. Its primary use is in the construction of the CI .yml files and simplify the management of many feedstocks.

conda-forge - the place where the feedstock and smithy live and work to produce the finished article (built conda distributions)

Updating podman-feedstock

If you would like to improve the podman recipe or build a new package version, please fork this repository and submit a PR. Upon submission, your changes will be run on the appropriate platforms to give the reviewer an opportunity to confirm that the changes result in a successful build. Once merged, the recipe will be re-built and uploaded automatically to the conda-forge channel, whereupon the built conda packages will be available for everybody to install and use from the conda-forge channel. Note that all branches in the conda-forge/podman-feedstock are immediately built and any created packages are uploaded, so PRs should be based on branches in forks and branches in the main repository should only be used to build distinct package versions.

In order to produce a uniquely identifiable distribution:

• If the version of a package is not being increased, please add or increase the build/number.
• If the version of a package is being increased, please remember to return the build/number back to 0.

Feedstock Maintainers

• @dhirschfeld
• @manics
• @mbargull
• @xhochy

podman-feedstock's Issues

Add support for podman for MacOS

Comment:

https://github.com/conda-forge/podman-feedstock/blob/main/recipe/meta.yaml#L20

currently, podman on conda-forge is supporting just linux machines.

would it be possible to add support for macos?
if yes, I would be happy to work on that.

thanks!

missing conda-forge package for `catatonit`

Comment:

When running podman pod create on podman >= 4.0.0, I run into this issue:

[16:55:23 | last: 12s] (  0) | ~
igozali@host $ podman pod create
Error: building local pause image: finding pause binary: exec: "catatonit": executable file not found in $PATH

Based on googling around, I found that there's a change in podman 4.0.0 where the default behavior is to not pull the infra image but build it locally to make podman run better on machines with no external network connection: containers/podman#12771 (comment)

I noticed there's no feedstock for catatonit, would it be a good idea to create one? In Ubuntu apt package for podman, they list catatonit as at least a recommended package https://packages.ubuntu.com/jammy/podman so we can build the infra image locally.

Workaround I've found so far is to revert to previous behavior to pull the infra image from public Docker repos: 89luca89/distrobox#667 (comment)

`WARN[0000]` "/" is not a shared mount, this could cause issues or missing mounts with rootless containers

Solution to issue cannot be found in the documentation.

• I checked the documentation.

Issue

I see the above error after installing podman and trying to run any command

Installed packages

-

Environment info

-

Can we default to overlayfs instead of vfs?

Comment:

The default storage driver is vfs which is inefficient since it'll create a copy of everything in each layer:

$ podman info -f '{{.Store.GraphDriverName}}'
vfs

overlayfs can be enabled by adding a configuration file:

mkdir -p ~/.config/containers
$ cat << EOF > ~/.config/containers/storage.conf
[storage]
driver = "overlay"
EOF

$ podman info -f '{{.Store.GraphDriverName}}'
overlay

Depending on the age of the kernel this may also require fuse-overlayfs.

fuse-overlayfs is available in conda-forge, though maintenance seems to have stopped over a year ago

Should `~.config/containers/storage.conf` be under conda `$PREFIX`?

Comment:

As noted in #28 (comment)
From the CI tests:

store:
  configFile: /home/conda/.config/containers/storage.conf

whereas other config files are under $PREFIX.

Should ~/.config/containers/storage.conf be changed to $PREFIX/share/containers/storage.conf to match the other configuration files which have been patched to be under $PREFIX, or is this is fine?

Error: cannot find newuidmap

https://github.com/containers/podman/blob/master/troubleshooting.md#9-newuidmap-missing-when-running-rootless-podman-commands

Is there some way to install these tools with conda so that podman Just Works out of the box?

Trouble finding `rootlessport`

Comment:

Error: could not find rootlessport in one of [/usr/local/libexec/podman /usr/local/lib/podman /usr/libexec/podman /usr/lib/podman]. To resolve this error, set the helper_binaries_dir key in the [engine] section of containers.conf to the directory containing your helper binaries

Binaries should be resolved using relative path

Solution to issue cannot be found in the documentation.

• I checked the documentation.

Issue

In Podman 4.0.0 some functionality was moved to a separate rootlessport executable https://github.com/containers/podman/releases/tag/v4.0.0
In the conda-forge package this is installed as $CONDA_PREFIX/libexec/podman/rootlessport

This results in errors with rootless port-forwarding:

$ podman run -it --rm -p 8000:8000 busybox

Error: could not find "rootlessport" in one of [/usr/local/libexec/podman /usr/local/lib/podman /usr/libexec/podman /usr/lib/podman].  To resolve this error, set the helper_binaries_dir key in the `[engine]` section of containers.conf to the directory containing your helper binaries.

The current patch changes Podman to use relative paths for config files, this patch needs to be extended to make the search path for executables relative too:

• https://github.com/containers/podman/blob/053b09660ffbe2df2104186c67e39be70764ff63/libpod/networking_slirp4netns.go#L550
• https://github.com/containers/podman/blob/053b09660ffbe2df2104186c67e39be70764ff63/vendor/github.com/containers/common/pkg/config/config.go#L1214-L1236

Installed packages

`podman version 4.1.0` from conda-forge

Environment info

N/A

@conda-forge-admin please add automerge

@conda-forge-admin please add bot automerge