apptainer(1)
π apptainer(1) β the manual page, bestie edition π
okay so you've stumbled into the apptainer(1) manual and specifically the registry login page, and honestly? you're in the right place. pull up a chair, grab a strawberry π, and let's get you logged in. no cap, this one's short and sweet.
β¨ NAME β¨
okay so the actual full name of this command is apptainer-registry-login β it's the part of apptainer that lets you login to an OCI/Docker registry. that's the whole vibe. she logs you in. π«Ά
πΈ SYNOPSIS πΈ
apptainer registry login [login options...]
literally just that. command, subcommand, and then your options go bopping along after it. iconic.
π¦ DESCRIPTION π¦
so the 'registry login' command is the one that lets you login to a specific OCI/Docker registry. that's it, that's the whole description, and honestly she ate. π
think of it as showing your ID at the door of the container registry club β once you're in, you're in.
β¨ OPTIONS β¨
here's the whole menu of flags, no skips, all of them, in order:
--authfile=""β the Docker-style authentication file to use for writing/reading OCI registry credentials. default is empty, i.e."". your little credential locker, basically. π-h,--help[=false]β help for login. default isfalse. when in doubt, ask for help, bestie. it's giving "just read the instructions" energy and we love that for us.-p,--password=""β the password / token to authenticate with. default"".--password-stdin[=false]β take the password from standard input. default isfalse. lowkey the safer vibe, iykyk. π₯-u,--username=""β the username to authenticate with, and heads up: this is required for Docker/OCI registry login. default"". yes, even when you're using a token. more on that below. π
π§ EXAMPLE π§
okay so the original example, verbatim, because precision is the moment:
To login in to a docker/OCI registry:
$ apptainer registry login --username foo docker://docker.io
$ apptainer registry login --username foo oras://myregistry.example.com
so you've got your docker:// registries and your oras:// registries, and either way you're passing --username foo. cute. simple. slay.
β οΈ and now the important part, bestie, read this twice:
many cloud OCI registries use token-based authentication. the token should be specified as the password for login. and even then β a username is still required. no username, no entry, periodt. π
so like, for the record: when using a standard Azure identity and token to login to an ACR registry, the username '00000000-0000-0000-0000-000000000000' is required. yes that's a real string, yes you have to type it exactly, no you can't skip it. π
and obviously consult your provider's documentation for the details concerning their specific login requirements β every registry's got its own little rules and honestly they all think they're the main character.
π SEE ALSO π
apptainer-registry(1)β go read the parent page too, the whole registry family is right there β¨
π HISTORY π
22-Oct-2026 β Auto generated by spf13/cobra. so yeah, this page literally wrote itself. auto-generated and still serving looks. π
and that's the whole page! π big sign-off energy: this beauty was Auto generated by spf13/cobra and dated Oct 2026, with apptainer(1) living up there in the corner the whole time. go log in, bestie, you're gonna do amazing π¦π
π¦ where this page comes from
- epel 9: apptainer 1.5.5-1.el9 Β· Apache-2.0 AND BSD-2-Clause AND BSD-3-Clause AND BSD-3-Clause-LBNL AND ISC AND MIT AND MPL-2.0 AND Unlicense
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms