podman-sys...ection-add(1)

πŸ“¦
version 6.1.4 Β· 6 versions
, in arch rolling, fedora 43, fedora 44, ubuntu resolute

πŸ’– podman-system-connection-add(1) πŸ’–

okay bestie, so this page lives in the General Commands Manual, and it's literally called podman-system-connection-add β€” say that five times fast, i can't 😭


✨ NAME ✨

podman-system-connection-add β€” record a destination for the Podman service πŸŽ€


✨ SYNOPSIS ✨

podman system connection add [options] name destination

✨ DESCRIPTION ✨

okay so real talk: this command records an ssh destination for remote podman service(s). it's giving "save this spot so i can get back to it later" energy. πŸ’…

the ssh destination you hand over has to be one of these four shapes, no cap:

  • [user@]hostname[:port]
  • ssh://[user@]hostname[:port]
  • unix://path
  • tcp://hostname:port

then, like, the user gets prompted for the remote ssh login password or the key file passphrase, whichever it needs at that moment. and yes, ssh-agent is supported if it's running. if it's not running, it can't help you, bestie, it's simply not invited to the party πŸ™ˆ


✨ OPTIONS ✨

  • --default, -d β€” makes the new destination the default for this user. the default is false. so like, by default it's not the default, which is a whole mood. ✨
  • --identity=path β€” path to the ssh identity file. if that identity file is encrypted, Podman prompts the user for the passphrase. if no identity file is provided and no user is given, Podman defaults to the user running the podman command. Podman prompts for the login password on the remote server. 🫢
  • --port, -p=port β€” port for the ssh destination. the default value is 22. πŸ‘‘
  • --socket-path=path β€” path to the Podman service unix domain socket on the ssh destination host. πŸ¦‹
  • --tls-ca=path β€” path to a PEM file containing the certificate authority bundle, used to verify the server's certificate against. 🌸
  • --tls-cert=path β€” path to a PEM file containing the TLS client certificate to present to the server. --tls-key must also be provided. they're a package deal, fr fr πŸ’–
  • --tls-key=path β€” path to a PEM file containing the private key matching --tls-cert. --tls-cert must also be provided. same deal, other direction, iconic πŸŽ€

✨ EXAMPLE ✨

add a named system connection:

$ podman system connection add QA podman.example.com

add a system connection using SSH data:

$ podman system connection add --identity ~/.ssh/dev_rsa production ssh://root@server.example.com:2222

add a named system connection to a local Unix domain socket:

$ podman system connection add testing unix:///run/podman/podman.sock

add a named system connection to a local tcp socket:

$ podman system connection add debug tcp://localhost:8080

add a connection with a custom port:

$ podman system connection add --port 2222 staging user@staging.example.com

add a connection with a custom socket path:

$ podman system connection add --socket-path /run/user/1000/podman/podman.sock remote-user user@remote.example.com

add a connection and make it the default:

$ podman system connection add --default production root@prod.example.com

add a named system connection to a remote tcp socket secured via TLS:

$ podman system connection add secure-debug --tls-cert=tls.crt --tls-key=tls.key --tls-ca=ca.crt tcp://podman.example.com:8443

✨ SEE ALSO ✨


✨ HISTORY ✨

June 2020, originally compiled by Jhon Honce (jhonce at redhat dot com) 🌈


and that's the whole page, bestie!! go forth and add connections, you absolute icon πŸ‘‘

that was podman-sys...ection-add(1) from the General Commands Manual, signing off πŸ’œ

πŸ“¦ where this page comes from