Skip to content
Introduction
Reference
Command line
dicer remote create

dicer remote create

Add a daemon to talk to

Synopsis

Add a daemon to talk to.

A unix:// socket is controlled by its file permissions: whoever can open it may do anything, and nothing further identifies either end.

A daemon’s TCP listener, HOST:PORT, is reached over TLS, or over nothing at all. With –tls-ca this client verifies the daemon and the connection is encrypted; with –tls-cert and –tls-key it identifies itself in turn, which a daemon configured with api.tcp.tls.client_ca_file requires. Given neither, the connection is plaintext and unauthenticated, so reach the daemon only over a network you trust as far as you trust the host.

The files are read on every connection, not copied here, so a renewed certificate is picked up without the remote being changed.

dicer remote create NAME ADDRESS [flags]

Examples 

  dicer remote create prod dicer1.example.com:7443 \
    --tls-ca ~/.dicer/ca.pem \
    --tls-cert ~/.dicer/client.pem --tls-key ~/.dicer/client-key.pem
  dicer remote create test unix:///run/dicer-test/dicer.sock

Options 

  -h, --help                     help for create
      --tls-ca string            Authorities the daemon's certificate is checked against, in PEM
      --tls-cert string          Certificate identifying this client to the daemon, in PEM
      --tls-key string           Private key for --tls-cert, in PEM
      --tls-server-name string   Name the daemon's certificate must carry, if not the host in ADDRESS

Options inherited from parent commands 

  -D, --debug              Trace every call to the daemon on stderr (or set $DICER_DEBUG)
  -r, --remote string      Daemon to talk to: a remote's name, or an address (unix:///PATH or HOST:PORT) (default $DICER_REMOTE, then the current remote, then local)
      --timeout duration   Give up on a call to the daemon after this long, e.g. 30s (0: never; streams such as logs -f and exec are not bounded)

SEE ALSO

dicer remotedicer remote delete