1buildah-login(1)            General Commands Manual           buildah-login(1)
2
3
4

NAME

6       buildah-login - Login to a container registry
7
8

SYNOPSIS

10       buildah login [options] registry
11
12

DESCRIPTION

14       buildah  login  logs  into a specified registry server with the correct
15       username and password. buildah login reads in the username and password
16       from  STDIN.  The username and password can also be set using the user‐
17       name and password flags.  The path of the authentication  file  can  be
18       specified  by  the  user by setting the authfile flag. The default path
19       used is ${XDG_RUNTIME_DIR}/containers/auth.json. If XDG_RUNTIME_DIR  is
20       not set, the default is /run/containers/$UID/auth.json.
21
22
23       buildah [GLOBAL OPTIONS]
24
25
26       buildah login [GLOBAL OPTIONS]
27
28
29       buildah login [OPTIONS] REGISTRY [GLOBAL OPTIONS]
30
31

OPTIONS

33       --authfile
34
35
36       Path  of  the  authentication file. Default is ${XDG_\RUNTIME_DIR}/con‐
37       tainers/auth.json. If  XDG_RUNTIME_DIR  is  not  set,  the  default  is
38       /run/user/$UID/containers/auth.json. This file is created using buildah
39       login.
40
41
42       Note: You can also override the default path of the authentication file
43       by  setting  the  REGISTRY_AUTH_FILE  environment variable. export REG‐
44       ISTRY_AUTH_FILE=path
45
46
47       --cert-dir path
48
49
50       Use certificates at path (*.crt, *.cert, *.key) to connect to the  reg‐
51       istry.  The default certificates directory is /etc/containers/certs.d.
52
53
54       --compat-auth-file=path
55
56
57       Instead  of  updating  the  default credentials file, update the one at
58       path, and use a Docker-compatible format.
59
60
61       --get-login
62
63
64       Return the logged-in user for the registry.  Return error if  no  login
65       is found.
66
67
68       --help, -h
69
70
71       Print usage statement
72
73
74       --password, -p
75
76
77       Password for registry
78
79
80       --password-stdin
81
82
83       Take the password from stdin
84
85
86       --tls-verify
87
88
89       Require  HTTPS  and  verification  of certificates when talking to con‐
90       tainer registries (default: true). If explicitly set to true, then  TLS
91       verification  will be used. If set to false, then TLS verification will
92       not be used. If not specified, TLS verification will be used unless the
93       target  registry  is listed as an insecure registry in registries.conf.
94       TLS verification cannot be used when talking to an insecure registry.
95
96
97       --username, -u
98
99
100       Username for registry
101
102
103       --verbose, -v
104
105
106       print detailed information about credential store
107
108

EXAMPLES

110              $ buildah login quay.io
111              Username: qiwanredhat
112              Password:
113              Login Succeeded!
114
115
116
117              $ buildah login -u testuser -p testpassword localhost:5000
118              Login Succeeded!
119
120
121
122              $ buildah login --authfile ./auth.json quay.io
123              Username: qiwanredhat
124              Password:
125              Login Succeeded!
126
127
128
129              $ buildah login --tls-verify=false -u test -p test localhost:5000
130              Login Succeeded!
131
132
133
134              $ buildah login --cert-dir /etc/containers/certs.d/ -u foo -p bar localhost:5000
135              Login Succeeded!
136
137
138
139              $ buildah login -u testuser  --password-stdin < pw.txt quay.io
140              Login Succeeded!
141
142
143
144              $ echo $testpassword | buildah login -u testuser --password-stdin quay.io
145              Login Succeeded!
146
147
148

SEE ALSO

150       buildah(1), buildah-logout(1)
151
152
153
154buildah                            Apr 2019                   buildah-login(1)