"Fossies" - the Fresh Open Source Software Archive

Member "buildah-1.27.2/docs/buildah-login.1.md" (20 Sep 2022, 2874 Bytes) of package /linux/misc/buildah-1.27.2.tar.gz:


As a special service "Fossies" has tried to format the requested source page into HTML format (assuming markdown format). Alternatively you can here view or download the uninterpreted source code file. A member file download can also be achieved by clicking within a package contents listing on the according byte size field.

buildah-login "1" "Apr 2019" "buildah"

NAME

buildah-login - Login to a container registry

SYNOPSIS

buildah login [options] registry

DESCRIPTION

buildah login logs into a specified registry server with the correct username and password. buildah login reads in the username and password from STDIN. The username and password can also be set using the username and password flags. The path of the authentication file can be specified by the user by setting the authfile flag. The default path used is **XDG_RUNTIMEDIR/containers/auth.json *  * .IfXDGRUNTIMEDIRisnotset, thedefaultis/run/containers/UID/auth.json.

buildah [GLOBAL OPTIONS]

buildah login [GLOBAL OPTIONS]

buildah login [OPTIONS] REGISTRY [GLOBAL OPTIONS]

OPTIONS

--authfile

Path of the authentication file. Default is ${XDG_\RUNTIME\_DIR}/containers/auth.json. If XDG_RUNTIME_DIR is not set, the default is /run/containers/$UID/auth.json. This file is created using buildah login.

Note: You can also override the default path of the authentication file by setting the REGISTRY_AUTH_FILE environment variable. export REGISTRY_AUTH_FILE=path

--cert-dir path

Use certificates at path (*.crt, *.cert, *.key) to connect to the registry. The default certificates directory is /etc/containers/certs.d.

--get-login

Return the logged-in user for the registry. Return error if no login is found.

--help, -h

Print usage statement

--password, -p

Password for registry

--password-stdin

Take the password from stdin

--tls-verify

Require HTTPS and verification of certificates when talking to container registries (default: true). If explicitly set to true, then TLS verification will be used. If set to false, then TLS verification will not be used. If not specified, TLS verification will be used unless the target registry is listed as an insecure registry in registries.conf. TLS verification cannot be used when talking to an insecure registry.

--username, -u

Username for registry

--verbose, -v

print detailed information about credential store

EXAMPLES

$ buildah login quay.io
Username: qiwanredhat
Password:
Login Succeeded!
$ buildah login -u testuser -p testpassword localhost:5000
Login Succeeded!
$ buildah login --authfile ./auth.json quay.io
Username: qiwanredhat
Password:
Login Succeeded!
$ buildah login --tls-verify=false -u test -p test localhost:5000
Login Succeeded!
$ buildah login --cert-dir /etc/containers/certs.d/ -u foo -p bar localhost:5000
Login Succeeded!
$ buildah login -u testuser  --password-stdin < pw.txt quay.io
Login Succeeded!
$ echo $testpassword | buildah login -u testuser --password-stdin quay.io
Login Succeeded!

SEE ALSO

buildah(1), buildah-logout(1)