SKOPEO-LOGIN(1)

💖 SKOPEO-LOGIN — ok bestie, let's get you logged in 💖

Manual page: skopeo-login(1) 🎀 part of the skopeo family, and yes it's the one that gets you into the club (aka your container registry).

---

✨ NAME ✨

skopeo-login — login to a container registry. that's it, that's the whole vibe 💅

---

🌸 SYNOPSIS 🌸

skopeo login [options] registry

---

🦋 DESCRIPTION 🦋

So basically: skopeo login logs you into a specified registry server with the correct username and password. It's giving "showing your ID at the door" energy 🫶

skopeo login reads the username and password from STDIN. no cap.

You can also set the username and password using the username and password flags if typing it into stdin isn't your moment.

And the path of the credentials file? You, yes you, can specify it by setting the authfile flag. main character control over your own credentials file ✨

---

👑 OPTIONS 👑

Heads up bestie: also see skopeo(1) for options placed before the subcommand name. iykyk 🧚

• --password, -p=password — password for the registry. literally just the password 🔑
• --password-stdin — take the password from stdin. feeding it in through the pipe instead of the command line, we love a discreet queen 🙈
• --username, -u=username — username for the registry 🎀
• --authfile=path — path of the managed registry credentials file. On Linux, the default is ${XDG_RUNTIME_DIR}/containers/auth.json. See containers-auth.json(5) for more details about the default on other platforms 🌈

The default value of this option is read from the REGISTRY_AUTH_FILE environment variable. yes, env var girlies, this one's for you 💜

• --compat-auth-file=path — instead of updating the default credentials file, update the one at path, and use a Docker-compatible format. it's giving "I speak Docker too" 🐳
• --get-login — return the logged-in user for the registry. Return error if no login is found. lowkey a vibe check on whether you're already in 😭
• --cert-dir=path — use certificates at path (*.crt, *.cert, *.key) to connect to the registry. Default certificates directory is /etc/containers/certs.d 📜
• --help, -h — print usage statement. the "help me bestie" flag 🫶
• --tls-verify=bool — require HTTPS and verify certificates when talking to the container registry or daemon. Default to registry.conf setting. security queen behavior, no skipping this unless you mean it 👑
• --verbose, -v — write more detailed information to stdout. not me wanting all the lore 📝

---

🍓 EXAMPLES 🍓

the classics, preserved exactly, because facts don't change even when the vibe does:

$ skopeo login docker.io
Username: testuser
Password:
Login Succeeded!

$ skopeo login -u testuser -p testpassword localhost:5000
Login Succeeded!

$ skopeo login --authfile authdir/myauths.json docker.io
Username: testuser
Password:
Login Succeeded!

$ skopeo login --tls-verify=false -u test -p test localhost:5000
Login Succeeded!

$ skopeo login --cert-dir /etc/containers/certs.d/ -u foo -p bar localhost:5000
Login Succeeded!

$ skopeo login -u testuser  --password-stdin < testpassword.txt docker.io
Login Succeeded!

$ echo $testpassword | skopeo login -u testuser --password-stdin docker.io
Login Succeeded!

ate. every single time 🔥

---

🌈 SEE ALSO 🌈

• skopeo(1)
• skopeo-logout(1)
• containers-auth.json(5)
• containers-registries.conf(5)
• containers-certs.d.5.md

go read your siblings, they're iconic too 💖

---

📜 HISTORY 📜

May 2020, Originally compiled by Qi Wang qiwan@redhat.com ⟨mailto:qiwan@redhat.com⟩

---

ok that's the whole page bestie, you're officially logged in and literate in skopeo-login(1) 💅✨ this was the skopeo-login(1) manual page (skopeo's own, from May 2020, originally compiled by Qi Wang) and honestly? iconic. periodt. 🎀🦋💜