buildah-login(1)

✨ buildah-login(1) ✨

okay bestie, welcome to the buildah-login page from the General Commands Manual — literally the glow-up your registry credentials deserve 💖

---

🎀 NAME 🎀

buildah-login — login to a container registry

no cap, that's the whole job. it gets you in. 🔑

---

🌸 SYNOPSIS 🌸

buildah login [options] registry

---

🦋 DESCRIPTION 🦋

okay so buildah login logs into a specified registry server with the correct username and password. it's giving main character energy at the front door of your registry 🚪✨

buildah login reads the username and password from STDIN. you can also set them with the username and password flags if typing into stdin isn't your vibe.

the path of the authentication file can be specified by you (yes, you) by setting the authfile flag. the default path used is ${XDG_RUNTIME_DIR}/containers/auth.json. and if XDG_RUNTIME_DIR is not set, the default is /run/user/$UID/containers/auth.json. so iconic of it to have a backup plan 💅

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. see containers-auth.json(5) for more info. this file is created using buildah login. lowkey it's born from your 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 — go off, customize your life 🌈

• --cert-dir path — use certificates at path (*.crt, *.cert, *.key) to connect to the registry. the default certificates directory is /etc/containers/certs.d. secure girl behavior 🔒
• --compat-auth-file=path — instead of updating the default credentials file, update the one at path, and use a Docker-compatible format. for when you gotta speak Docker's language 🐳
• --get-login — return the logged-in user for the registry. return error if no login is found. it's giving "who even are you" 😭
• --help, -h — print usage statement. the classic. the icon. 📖
• --password, -p — password for registry 🔐
• --password-stdin — take the password from stdin. pipe it in, don't say it out loud bestie 🤫
• --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. so don't try it, fr fr 🚫
• --username, -u — username for registry 🙋
• --verbose, -v — print detailed information about credential store. spill the tea, 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 that Login Succeeded!? that's the serotonin. every single time. 🌟

---

👑 SEE ALSO 👑

buildah(1), buildah-logout(1), containers-auth.json(5)

like, go read your siblings too, they're all iconic 🫶

---

aaaand that's the whole page, bestie 💖 this one's brought to you by buildah, dated Apr 2019 — old but still absolutely eating, no cap. mwah, go log in somewhere cute 💅✨🌈