# packages

pkgId: e660f1b6664a19fe115505b3d795cd787a5bec6d483575171cc60a34580a8925
name: docker-logrotate
arch: x86_64
version: 1.13.1
epoch: 2
release: 48.git4032bd5.el7
summary: cron job to run logrotate on Docker containers
url: https://github.com/projectatomic/docker
rpm_license: ASL 2.0
rpm_vendor: CentOS
rpm_group: Unspecified
rpm_buildhost: c1bk.rdu2.centos.org
rpm_sourcerpm: docker-1.13.1-48.git4032bd5.el7.src.rpm
rpm_packager: CBS <cbs@centos.org>
location_href: docker-logrotate-1.13.1-48.git4032bd5.el7.x86_64.rpm
checksum_type: sha256
description:
  This package installs cron job to run logrotate on Docker containers. logrotate is assumed to be installed on
  containers for this to work, failures are silently ignored.


pkgId: d74abc59cd6a5ea776bb63d4cce36abf3ec33188a5790000cc1db929b1e86852
name: python2-docker
arch: noarch
version: 2.5.1
epoch: 0
release: 2.el7
summary: A Python library for the Docker Engine API
url: https://pypi.python.org/pypi/docker
rpm_license: ASL 2.0
rpm_vendor: CentOS
rpm_group: Unspecified
rpm_buildhost: c1bk.rdu2.centos.org
rpm_sourcerpm: python-docker-2.5.1-2.el7.src.rpm
rpm_packager: CBS <cbs@centos.org>
location_href: python2-docker-2.5.1-2.el7.noarch.rpm
checksum_type: sha256
description:
  It lets you do anything the docker command does, but from within Python apps –
  run containers, manage containers, manage Swarms, etc.


pkgId: c3f1c591284a8246a3c7e149095a760858ed8341bd09383befc8949365a187aa
name: podman
arch: x86_64
version: 0.4.2
epoch: 0
release: 6.git864b9c0.el7
summary: Manage Pods, Containers and Container Images
url: %{git_podman}
rpm_license: ASL 2.0
rpm_vendor: CentOS
rpm_group: Unspecified
rpm_buildhost: c1bj.rdu2.centos.org
rpm_sourcerpm: podman-0.4.2-6.git864b9c0.el7.src.rpm
rpm_packager: CBS <cbs@centos.org>
location_href: podman-0.4.2-6.git864b9c0.el7.x86_64.rpm
checksum_type: sha256
description:
  Manage Pods, Containers and Container Images
  libpod provides a library for applications looking to use
  the Container Pod concept popularized by Kubernetes.


pkgId: bad2a16d34f4942c78a1c78a291fcd43c977db7b049dfd5d266e60eab9bf32f3
name: atomic
arch: x86_64
version: 1.20.1
epoch: 0
release: 2.el7
summary: Tool for managing ProjectAtomic systems and containers
url: https://github.com/projectatomic/atomic
rpm_license: LGPLv2+
rpm_vendor: CentOS
rpm_group: Unspecified
rpm_buildhost: c1bd.rdu2.centos.org
rpm_sourcerpm: atomic-1.20.1-2.el7.src.rpm
rpm_packager: CBS <cbs@centos.org>
location_href: atomic-1.20.1-2.el7.x86_64.rpm
checksum_type: sha256
description:
  The goal of Atomic is to provide a high level, coherent entrypoint to the
  system, and fill in gaps.

  atomic can make it easier to interact with container runtimes for different
  kinds of containers, such as super-privileged and system containers.

  The atomic host subcommand wraps rpm-ostree providing unified management.


pkgId: 6bdc105afba4dce2e7874118f6faea5cf4195bfbfab22a4a81eac4409ddce6a8
name: containernetworking-plugins
arch: x86_64
version: 0.8.3
epoch: 0
release: 2.el7
summary: Libraries for writing CNI plugin
url: https://github.com/containernetworking/plugins
rpm_license: ASL 2.0
rpm_vendor: CentOS
rpm_group: Unspecified
rpm_buildhost: c1bd.rdu2.centos.org
rpm_sourcerpm: containernetworking-plugins-0.8.3-2.el7.src.rpm
rpm_packager: CBS <cbs@centos.org>
location_href: containernetworking-plugins-0.8.3-2.el7.x86_64.rpm
checksum_type: sha256
description:
  The CNI (Container Network Interface) project consists of a specification
  and libraries for writing plugins to configure network interfaces in Linux
  containers, along with a number of supported plugins. CNI concerns itself
  only with network connectivity of containers and removing allocated resources
  when the container is deleted.


pkgId: 8bda663703ead4ff0de1901f60304958ba41dee2b2984f648b9e7b410daecb2b
name: containernetworking-plugins-unit-test-devel
arch: x86_64
version: 0.8.3
epoch: 0
release: 2.el7
summary: Unit tests for containernetworking-plugins package
url: https://github.com/containernetworking/plugins
rpm_license: ASL 2.0
rpm_vendor: CentOS
rpm_group: Unspecified
rpm_buildhost: c1bd.rdu2.centos.org
rpm_sourcerpm: containernetworking-plugins-0.8.3-2.el7.src.rpm
rpm_packager: CBS <cbs@centos.org>
location_href: containernetworking-plugins-unit-test-devel-0.8.3-2.el7.x86_64.rpm
checksum_type: sha256
description:
  This package contains unit tests for project
  providing packages with github.com/containernetworking/plugins prefix.


pkgId: 2803f520300414034909f7fdf039325494dee17d75e9d0bc0bcb73972e89f692
name: docker-common
arch: x86_64
version: 1.13.1
epoch: 2
release: 87.git07f3374.el7
summary: Common files for docker and docker-latest
url: https://github.com/docker/docker
rpm_license: ASL 2.0
rpm_vendor: CentOS
rpm_group: Unspecified
rpm_buildhost: c1bj.rdu2.centos.org
rpm_sourcerpm: docker-1.13.1-87.git07f3374.el7.src.rpm
rpm_packager: CBS <cbs@centos.org>
location_href: docker-common-1.13.1-87.git07f3374.el7.x86_64.rpm
checksum_type: sha256
description:
  This package contains the common files /usr/bin/docker which will point to
  /usr/bin/docker-current or /usr/bin/docker-latest configurable via
  /etc/sysconfig/docker


pkgId: e9749cd56b19a3dd23e69f00b4d7cfb13f8fa5da615e403f412c69242baf5c7c
name: docker-novolume-plugin
arch: x86_64
version: 1.13.1
epoch: 2
release: 69.gitdded712.el7
summary: Block container starts with local volumes defined
url: https://github.com/projectatomic/docker-novolume-plugin
rpm_license: MIT
rpm_vendor: CentOS
rpm_group: Unspecified
rpm_buildhost: c1be.rdu2.centos.org
rpm_sourcerpm: docker-1.13.1-69.gitdded712.el7.src.rpm
rpm_packager: CBS <cbs@centos.org>
location_href: docker-novolume-plugin-1.13.1-69.gitdded712.el7.x86_64.rpm
checksum_type: sha256
description:
  When a volume in provisioned via the `VOLUME` instruction in a Dockerfile or
  via `docker run -v volumename`, host's storage space is used. This could lead to
  an unexpected out of space issue which could bring down everything.
  There are situations where this is not an accepted behavior. PAAS, for
  instance, can't allow their users to run their own images without the risk of
  filling the entire storage space on a server. One solution to this is to deny users
  from running images with volumes. This way the only storage a user gets can be limited
  and PAAS can assign quota to it.

  This plugin solves this issue by disallowing starting a container with
  local volumes defined. In particular, the plugin will block `docker run` with:

  - `--volumes-from`
  - images that have `VOLUME`(s) defined
  - volumes early provisioned with `docker volume` command

  The only thing allowed will be just bind mounts.


pkgId: 61920500575cdf7a575211a52aa21402b7cd48fb6b7d661675b445e59edb3298
name: docker-rhsubscription
arch: x86_64
version: 1.13.1
epoch: 2
release: 25.gitb5e3294.el7
summary: Red Hat subscription management files needed on the host to enable RHEL containers
url: https://github.com/projectatomic/docker
rpm_license: ASL 2.0
rpm_vendor: CentOS
rpm_group: Unspecified
rpm_buildhost: c1be.rdu2.centos.org
rpm_sourcerpm: docker-1.13.1-25.gitb5e3294.el7.src.rpm
rpm_packager: CBS <cbs@centos.org>
location_href: docker-rhsubscription-1.13.1-25.gitb5e3294.el7.x86_64.rpm
checksum_type: sha256
description:
  In order to work with RHEL containers, the host (RHEL, or other) must export susbcription information to the container.


pkgId: b005cf1798da134a582347b70e85e86b505e0d27e183e01a258f1a15d5c3f248
name: docker-rhel-push-plugin
arch: x86_64
version: 1.13.1
epoch: 2
release: 92.gitb2f74b2.el7
summary: Avoids pushing a RHEL-based image to docker.io registry
url: https://github.com/docker/docker
rpm_license: GPLv2
rpm_vendor: CentOS
rpm_group: Unspecified
rpm_buildhost: c1bd.rdu2.centos.org
rpm_sourcerpm: docker-1.13.1-92.gitb2f74b2.el7.src.rpm
rpm_packager: CBS <cbs@centos.org>
location_href: docker-rhel-push-plugin-1.13.1-92.gitb2f74b2.el7.x86_64.rpm
checksum_type: sha256
description:
  In order to use this plugin you must be running at least Docker 1.10 which
  has support for authorization plugins.

  This plugin avoids any RHEL based image to be pushed to the default docker.io
  registry preventing users to violate the RH subscription agreement.


pkgId: 30b97dcab60a9d69fdff17c0ba91cb9b28733009eebbaf6d17199df36c90f2db
name: buildah
arch: x86_64
version: 1.11.4
epoch: 0
release: 3.el7
summary: A command line tool used for creating OCI Images
url: https://buildah.io
rpm_license: ASL 2.0
rpm_vendor: CentOS
rpm_group: Unspecified
rpm_buildhost: c1be.rdu2.centos.org
rpm_sourcerpm: buildah-1.11.4-3.el7.src.rpm
rpm_packager: CBS <cbs@centos.org>
location_href: buildah-1.11.4-3.el7.x86_64.rpm
checksum_type: sha256
description:
  The buildah package provides a command line tool which can be used to
  * create a working container from scratch
  or
  * create a working container from an image as a starting point
  * mount/umount a working container's root file system for manipulation
  * save container's root file system layer to create a new image
  * delete a working container or an image


pkgId: d1123a72575c94759e301fbde75b7f036144c8111f1f77381b6bbf44b8004d1c
name: runc
arch: x86_64
version: 1.0.0
epoch: 0
release: 55.dev.git2abd837.el7
summary: CLI for running Open Containers
url: http//github.com/opencontainers/runc
rpm_license: ASL 2.0
rpm_vendor: CentOS
rpm_group: Unspecified
rpm_buildhost: c1bj.rdu2.centos.org
rpm_sourcerpm: runc-1.0.0-55.dev.git2abd837.el7.src.rpm
rpm_packager: CBS <cbs@centos.org>
location_href: runc-1.0.0-55.dev.git2abd837.el7.x86_64.rpm
checksum_type: sha256
description:
  The runc command can be used to start containers which are packaged
  in accordance with the Open Container Initiative's specifications,
  and to manage containers running under runc.


pkgId: 905bd29043f86080e8bd44eefbe19b06c9a2aabb9e479bd39effd10f437d7511
name: docker-lvm-plugin
arch: x86_64
version: 1.13.1
epoch: 2
release: 42.git4402c09.el7
summary: Docker volume driver for lvm volumes
url: https://github.com/projectatomic/docker
rpm_license: LGPLv3
rpm_vendor: CentOS
rpm_group: Unspecified
rpm_buildhost: c1bd.rdu2.centos.org
rpm_sourcerpm: docker-1.13.1-42.git4402c09.el7.src.rpm
rpm_packager: CBS <cbs@centos.org>
location_href: docker-lvm-plugin-1.13.1-42.git4402c09.el7.x86_64.rpm
checksum_type: sha256
description:
  Docker Volume Driver for lvm volumes.

  This plugin can be used to create lvm volumes of specified size, which can
  then be bind mounted into the container using `docker run` command.


pkgId: 737af6add5c0dd4fc79afa374cdd4223826da5f0862a7c6cfd7f0c2d97a42309
name: docker
arch: x86_64
version: 1.13.1
epoch: 2
release: 69.gitdded712.el7
summary: Automates deployment of containerized applications
url: https://github.com/docker/docker
rpm_license: ASL 2.0
rpm_vendor: CentOS
rpm_group: Unspecified
rpm_buildhost: c1be.rdu2.centos.org
rpm_sourcerpm: docker-1.13.1-69.gitdded712.el7.src.rpm
rpm_packager: CBS <cbs@centos.org>
location_href: docker-1.13.1-69.gitdded712.el7.x86_64.rpm
checksum_type: sha256
description:
  Docker is an open-source engine that automates the deployment of any
  application as a lightweight, portable, self-sufficient container that will
  run virtually anywhere.

  Docker containers can encapsulate any payload, and will run consistently on
  and between virtually any server. The same container that a developer builds
  and tests on a laptop will run at scale, in production*, on VMs, bare-metal
  servers, OpenStack clusters, public instances, or combinations of the above.


pkgId: 37f47c1bfd0623934cd108578d61cb3cace7881852a2e5e663ee1ffa6d48c80d
name: skopeo-containers
arch: x86_64
version: 0.1.31
epoch: 1
release: 1.gitf9baaa6.el7
summary: Configuration files for working with image signatures
url: https://github.com/projectatomic/skopeo
rpm_license: ASL 2.0
rpm_vendor: CentOS
rpm_group: Unspecified
rpm_buildhost: c1be.rdu2.centos.org
rpm_sourcerpm: skopeo-0.1.31-1.gitf9baaa6.el7.src.rpm
rpm_packager: CBS <cbs@centos.org>
location_href: skopeo-containers-0.1.31-1.gitf9baaa6.el7.x86_64.rpm
checksum_type: sha256
description:
  This package installs a default signature store configuration and a default
  policy under `/etc/containers/`.


pkgId: b2b528b130f3b431e5057890a3746565e27df4edb54a120e9ba3511beba4056c
name: buildah
arch: x86_64
version: 1.4
epoch: 0
release: 2.git608fa84.el7
summary: A command line tool used for creating OCI Images
url: https://github.com/containers/buildah
rpm_license: ASL 2.0
rpm_vendor: CentOS
rpm_group: Unspecified
rpm_buildhost: c1bj.rdu2.centos.org
rpm_sourcerpm: buildah-1.4-2.git608fa84.el7.src.rpm
rpm_packager: CBS <cbs@centos.org>
location_href: buildah-1.4-2.git608fa84.el7.x86_64.rpm
checksum_type: sha256
description:
  The buildah package provides a command line tool which can be used to
  * create a working container from scratch
  or
  * create a working container from an image as a starting point
  * mount/umount a working container's root file system for manipulation
  * save container's root file system layer to create a new image
  * delete a working container or an image

  %enable_gotoolset7


pkgId: b1dabebd971ef23064cf54c36a45af51a039f8483a0ed3eda0d18a5d29adbd70
name: docker-unit-test
arch: x86_64
version: 1.13.1
epoch: 2
release: 72.git6f36bd4.el7
summary: Automates deployment of containerized applications - for running unit tests
url: https://github.com/docker/docker
rpm_license: ASL 2.0
rpm_vendor: CentOS
rpm_group: Unspecified
rpm_buildhost: c1bd.rdu2.centos.org
rpm_sourcerpm: docker-1.13.1-72.git6f36bd4.el7.src.rpm
rpm_packager: CBS <cbs@centos.org>
location_href: docker-unit-test-1.13.1-72.git6f36bd4.el7.x86_64.rpm
checksum_type: sha256
description:
  Automates deployment of containerized applications - for running unit tests - for running unit tests


pkgId: 537b96c741cb8dc04384ec5579b74bb268415487fca4e81fbab0b5ba1b93f3cc
name: container-storage-setup
arch: noarch
version: 0.11.0
epoch: 0
release: 2.git5eaf76c.el7
summary: A simple service to setup container storage devices
url: https://github.com/projectatomic/container-storage-setup
rpm_license: ASL 2.0
rpm_vendor: CentOS
rpm_group: Unspecified
rpm_buildhost: c1bj.rdu2.centos.org
rpm_sourcerpm: container-storage-setup-0.11.0-2.git5eaf76c.el7.src.rpm
rpm_packager: CBS <cbs@centos.org>
location_href: container-storage-setup-0.11.0-2.git5eaf76c.el7.noarch.rpm
checksum_type: sha256
description:
  This is a simple service to configure Container Runtimes to use an LVM-managed
  thin pool.  It also supports auto-growing both the pool as well
  as the root logical volume and partition table.


pkgId: a2369f2dd98645f4cb6db529d2cbcee65b14e6341790147a4e1abc61f1257fc0
name: podman-docker
arch: noarch
version: 0.12.1.2
epoch: 0
release: 2.git9551f6b.el7
summary: Emulate Docker CLI using podman
url: https://github.com/containers/libpod
rpm_license: ASL 2.0
rpm_vendor: CentOS
rpm_group: Unspecified
rpm_buildhost: c1bj.rdu2.centos.org
rpm_sourcerpm: podman-0.12.1.2-2.git9551f6b.el7.src.rpm
rpm_packager: CBS <cbs@centos.org>
location_href: podman-docker-0.12.1.2-2.git9551f6b.el7.noarch.rpm
checksum_type: sha256
description:
  This package installs a script named docker that emulates the Docker CLI by
  executing podman commands, it also creates links between all Docker CLI man
  pages and podman.


pkgId: dc97b486b760eb7ab9d3a0d7609d2e9a7d3f7bef02c3b61953f8f8e5243b9327
name: libseccomp-devel
arch: x86_64
version: 2.4.1
epoch: 0
release: 0.el7
summary: Development files used to build applications with libseccomp support
url: https://github.com/seccomp/libseccomp
rpm_license: LGPLv2
rpm_vendor: CentOS
rpm_group: Unspecified
rpm_buildhost: c1bd.rdu2.centos.org
rpm_sourcerpm: libseccomp-2.4.1-0.el7.src.rpm
rpm_packager: CBS <cbs@centos.org>
location_href: libseccomp-devel-2.4.1-0.el7.x86_64.rpm
checksum_type: sha256
description:
  The libseccomp library provides an easy to use interface to the Linux Kernel's
  syscall filtering mechanism, seccomp.  The libseccomp API allows an application
  to specify which syscalls, and optionally which syscall arguments, the
  application is allowed to execute, all of which are enforced by the Linux
  Kernel.


pkgId: 618711f5d84d056afbb5239ec05765d486122108c5c164dd188543df6a2d08c7
name: podman-docker
arch: noarch
version: 1.4.0
epoch: 0
release: 2.el7
summary: Emulate Docker CLI using podman
url: https://podman.io/
rpm_license: ASL 2.0
rpm_vendor: CentOS
rpm_group: Unspecified
rpm_buildhost: c1bj.rdu2.centos.org
rpm_sourcerpm: podman-1.4.0-2.el7.src.rpm
rpm_packager: CBS <cbs@centos.org>
location_href: podman-docker-1.4.0-2.el7.noarch.rpm
checksum_type: sha256
description:
  This package installs a script named docker that emulates the Docker CLI by
  executes podman commands, it also creates links between all Docker CLI man
  pages and podman.


pkgId: aad3471a36a3a882822318b2a8aac637e14d25bce0b56fcc48792203f4ae0cff
name: podman
arch: x86_64
version: 1.4.0
epoch: 0
release: 2.el7
summary: Manage Pods, Containers and Container Images
url: https://podman.io/
rpm_license: ASL 2.0
rpm_vendor: CentOS
rpm_group: Unspecified
rpm_buildhost: c1bj.rdu2.centos.org
rpm_sourcerpm: podman-1.4.0-2.el7.src.rpm
rpm_packager: CBS <cbs@centos.org>
location_href: podman-1.4.0-2.el7.x86_64.rpm
checksum_type: sha256
description:
  podman (Pod Manager) is a fully featured container engine that is a simple daemonless tool.  podman provides a Docker-CLI comparable command line that eases the transition from other container engines and allows the management of pods, containers and images.  Simply put: alias docker=podman.  Most podman commands can be run as a regular user, without requiring additional privileges.

  podman uses Buildah(1) internally to create container images. Both tools share image (not container) storage, hence each can use or manipulate images (but not containers) created by the other.

  Manage Pods, Containers and Container Images
  libpod Simple management tool for pods, containers and images


pkgId: 9aebd273e0eddb18567749cce69001a79ae8586914a5edf6cc232f2663e0be47
name: skopeo
arch: x86_64
version: 0.1.31
epoch: 1
release: 1.gitf9baaa6.el7
summary: Inspect Docker images and repositories on registries
url: https://github.com/projectatomic/skopeo
rpm_license: ASL 2.0
rpm_vendor: CentOS
rpm_group: Unspecified
rpm_buildhost: c1be.rdu2.centos.org
rpm_sourcerpm: skopeo-0.1.31-1.gitf9baaa6.el7.src.rpm
rpm_packager: CBS <cbs@centos.org>
location_href: skopeo-0.1.31-1.gitf9baaa6.el7.x86_64.rpm
checksum_type: sha256
description:
  Command line utility to inspect images and repositories directly on Docker
  registries without the need to pull them


pkgId: d1966351a914096c121188ecf6f782d9b3e7c245e5e017077619b6af872fe18b
name: docker-lvm-plugin
arch: x86_64
version: 1.13.1
epoch: 2
release: 87.git07f3374.el7
summary: Docker volume driver for lvm volumes
url: https://github.com/docker/docker
rpm_license: LGPLv3
rpm_vendor: CentOS
rpm_group: Unspecified
rpm_buildhost: c1bj.rdu2.centos.org
rpm_sourcerpm: docker-1.13.1-87.git07f3374.el7.src.rpm
rpm_packager: CBS <cbs@centos.org>
location_href: docker-lvm-plugin-1.13.1-87.git07f3374.el7.x86_64.rpm
checksum_type: sha256
description:
  Docker Volume Driver for lvm volumes.

  This plugin can be used to create lvm volumes of specified size, which can
  then be bind mounted into the container using `docker run` command.

  %enable_gotoolset7


pkgId: aa4c4fdd7518a922b260635f83954fd32e5c6c70ec099f96259930b9dd10c8a3
name: docker-v1.10-migrator
arch: x86_64
version: 1.13.1
epoch: 2
release: 87.git07f3374.el7
summary: Calculates SHA256 checksums for docker layer content
url: https://github.com/docker/docker
rpm_license: ASL 2.0 and CC-BY-SA
rpm_vendor: CentOS
rpm_group: Unspecified
rpm_buildhost: c1bj.rdu2.centos.org
rpm_sourcerpm: docker-1.13.1-87.git07f3374.el7.src.rpm
rpm_packager: CBS <cbs@centos.org>
location_href: docker-v1.10-migrator-1.13.1-87.git07f3374.el7.x86_64.rpm
checksum_type: sha256
description:
  Starting from v1.10 docker uses content addressable IDs for the images and
  layers instead of using generated ones. This tool calculates SHA256 checksums
  for docker layer content, so that they don't need to be recalculated when the
  daemon starts for the first time.

  The migration usually runs on daemon startup but it can be quite slow(usually
  100-200MB/s) and daemon will not be able to accept requests during
  that time. You can run this tool instead while the old daemon is still
  running and skip checksum calculation on startup.


pkgId: 95b70d3fd83d96d26303650b1f45498e5051f8318b7651509557bed5d75974e5
name: python-backports-ssl_match_hostname
arch: noarch
version: 3.5.0.1
epoch: 0
release: 1.el7
summary: The ssl.match_hostname() function from Python 3
url: https://bitbucket.org/brandon/backports.ssl_match_hostname
rpm_license: Python
rpm_vendor: CentOS
rpm_group: Unspecified
rpm_buildhost: c1be.rdu2.centos.org
rpm_sourcerpm: python-backports-ssl_match_hostname-3.5.0.1-1.el7.src.rpm
rpm_packager: CBS <cbs@centos.org>
location_href: python-backports-ssl_match_hostname-3.5.0.1-1.el7.noarch.rpm
checksum_type: sha256
description:
  The Secure Sockets layer is only actually secure if you check the hostname in
  the certificate returned by the server to which you are connecting, and verify
  that it matches to hostname that you are trying to reach.

  But the matching logic, defined in RFC2818, can be a bit tricky to implement on
  your own. So the ssl package in the Standard Library of Python 3.2 now includes
  a match_hostname() function for performing this check instead of requiring
  every application to implement the check separately.

  This backport brings match_hostname() to users of earlier versions of Python.
  The actual code is only slightly modified from Python 3.5.


pkgId: e99262e5f525835d294313f784e3b44f474fe84c9b3ddd850b8ddf8bb01a7b67
name: containernetworking-plugins-devel
arch: noarch
version: 0.8.3
epoch: 0
release: 2.el7
summary: Libraries for writing CNI plugin
url: https://github.com/containernetworking/plugins
rpm_license: ASL 2.0
rpm_vendor: CentOS
rpm_group: Unspecified
rpm_buildhost: c1bd.rdu2.centos.org
rpm_sourcerpm: containernetworking-plugins-0.8.3-2.el7.src.rpm
rpm_packager: CBS <cbs@centos.org>
location_href: containernetworking-plugins-devel-0.8.3-2.el7.noarch.rpm
checksum_type: sha256
description:
  This package contains library source intended for
  building other packages which use import path with
  github.com/containernetworking/plugins prefix.


pkgId: 9dcadd9a93ba05901295d16ec68f1feb33e989b660c35f87e8db580e8e2d42be
name: podman
arch: x86_64
version: 1.6.2
epoch: 0
release: 3.el7
summary: Manage Pods, Containers and Container Images
url: https://podman.io/
rpm_license: ASL 2.0
rpm_vendor: CentOS
rpm_group: Unspecified
rpm_buildhost: c1bk.rdu2.centos.org
rpm_sourcerpm: podman-1.6.2-3.el7.src.rpm
rpm_packager: CBS <cbs@centos.org>
location_href: podman-1.6.2-3.el7.x86_64.rpm
checksum_type: sha256
description:
  podman (Pod Manager) is a fully featured container engine that is a simple
  daemonless tool.  podman provides a Docker-CLI comparable command line that
  eases the transition from other container engines and allows the management of
  pods, containers and images.  Simply put: alias docker=podman.
  Most podman commands can be run as a regular user, without requiring additional privileges.

  podman uses Buildah(1) internally to create container images. Both tools share image (not container) storage, hence each can use or manipulate images (but not containers) created by the other.

  Manage Pods, Containers and Container Images
  libpod Simple management tool for pods, containers and images


pkgId: c3710dc4af6980f011a709b786a21963ba0ae5e4a5e64c0277d4cb4dcc2c2f0e
name: docker-compose
arch: noarch
version: 1.16.1
epoch: 0
release: 2.el7
summary: Multi-container orchestration for Docker
url: https://github.com/docker/compose
rpm_license: ASL 2.0
rpm_vendor: CentOS
rpm_group: Unspecified
rpm_buildhost: c1bk.rdu2.centos.org
rpm_sourcerpm: docker-compose-1.16.1-2.el7.src.rpm
rpm_packager: CBS <cbs@centos.org>
location_href: docker-compose-1.16.1-2.el7.noarch.rpm
checksum_type: sha256
description:
  Compose is a tool for defining and running multi-container Docker
  applications. With Compose, you use a Compose file to configure your
  application's services. Then, using a single command, you create and
  start all the services from your configuration.

  Compose is great for development, testing, and staging environments,
  as well as CI workflows.

  Using Compose is basically a three-step process.

  1. Define your app's environment with a Dockerfile so it can be
     reproduced anywhere.
  2. Define the services that make up your app in docker-compose.yml so
     they can be run together in an isolated environment:
  3. Lastly, run docker-compose up and Compose will start and run your
     entire app.


