Gentoo Packages

Search

Install

Install this package:

emerge -a app-containers/docker-pushrm

If the package is masked, you can unmask it using the autounmask tool or standard emerge options:

autounmask app-containers/docker-pushrm

Or alternatively:

emerge --autounmask-write -a app-containers/docker-pushrm

Package Information

Description:

docker-pushrm is a Docker CLI plugin that adds a new docker pushrm command to Docker. It pushes the README file from the current working directory to a container registry server where it appears as repo description in the web interface. It currently supports Docker Hub, Red Hat Quay and Harbor v2. For most registry types docker-pushrm uses authentication info from the Docker credentials store - so it "just works" for registry servers that you're already logged into with Docker.

Homepage:

https://github.com/docker/buildx

License:

MIT

Versions

Metadata

Description

• docker-pushrm is a Docker CLI plugin that adds a new docker pushrm command to Docker. It pushes the README file from the current working directory to a container registry server where it appears as repo description in the web interface. It currently supports Docker Hub, Red Hat Quay and Harbor v2. For most registry types docker-pushrm uses authentication info from the Docker credentials store - so it "just works" for registry servers that you're already logged into with Docker.

Maintainers

• Maciej Barć (xgqt@gentoo.org) - Type: person

Upstream

• Bugs: https://github.com/christian-korneck/docker-pushrm/issues/
• Remote IDs:
  • github: christian-korneck/docker-pushrm

<pkgmetadata>
	<maintainer type="person">
		<email>xgqt@gentoo.org</email>
		<name>Maciej Barć</name>
	</maintainer>
	<longdescription lang="en">
    docker-pushrm is a Docker CLI plugin that adds a new docker pushrm
    command to Docker.  It pushes the README file from the current working
    directory to a container registry server where it appears as repo
    description in the web interface.  It currently supports Docker Hub, Red
    Hat Quay and Harbor v2.  For most registry types docker-pushrm uses
    authentication info from the Docker credentials store - so it "just
    works" for registry servers that you're already logged into with Docker.
  </longdescription>
	<upstream>
		<bugs-to>https://github.com/christian-korneck/docker-pushrm/issues/</bugs-to>
		<remote-id type="github">christian-korneck/docker-pushrm</remote-id>
	</upstream>
</pkgmetadata>

Lint Warnings

• [Error] Missing md5-cache for ebuild docker-pushrm-1.9.0

Manifest