.nh
.TH "singularity" "1" "Feb 2022" "Auto generated by spf13/cobra" ""

.SH NAME
.PP
singularity-remote-login - Login to a singularity remote endpoint, an OCI/Docker registry or a keyserver using credentials


.SH SYNOPSIS
.PP
\fBsingularity remote login [login options...] \fP


.SH DESCRIPTION
.PP
The 'remote login' command allows you to set credentials for a specific endpoint,
  an OCI/Docker registry or a keyserver.

.PP
If no endpoint or registry is specified, the command will login to the currently
  active remote endpoint. This is cloud.sylabs.io by default.


.SH OPTIONS
.PP
\fB-h\fP, \fB--help\fP[=false]
	help for login

.PP
\fB-i\fP, \fB--insecure\fP[=false]
	allow insecure login

.PP
\fB-p\fP, \fB--password\fP=""
	password / token to authenticate with

.PP
\fB--password-stdin\fP[=false]
	take password from standard input

.PP
\fB--tokenfile\fP=""
	path to the file holding auth token for login (remote endpoints only)

.PP
\fB-u\fP, \fB--username\fP=""
	username to authenticate with (required for Docker/OCI registry login)


.SH EXAMPLE
.PP
.RS

.nf

  To log in to an endpoint:
  $ singularity remote login SylabsCloud

  To login in to a docker/OCI registry:
  $ singularity remote login --username foo docker://docker.io
  $ singularity remote login --username foo oras://myregistry.example.com

  Note that many cloud OCI registries use token based authentication. The token
  should be specified as the password for login. A username is still required. E.g.
  when using a standard Azure identity and token to login to an ACR registry the
  username '00000000-0000-0000-0000-000000000000' is required. Consult your provider
  documentation for detail of their login requirements.

.fi
.RE


.SH SEE ALSO
.PP
\fBsingularity-remote(1)\fP


.SH HISTORY
.PP
20-Feb-2022 Auto generated by spf13/cobra