You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
msgid "The TLS certificates used for the *etcd* service, web API and the client authentication certificate, must both contain a valid Subject Alternative Name (SAN). Otherwise the *etcd* service will reject them as invalid."
msgid "The system configuration, keys and certificates are stored in an etcd database. The etcd service stores the database in the ``/data`` path of the container. Container executors allow to volume or bind mount this path."
msgid "The production container supports two `modes of operation <production-image.html#Modes of Operation>`__. The following chapters describe how to run the container with the provided compose files or with the *run* command."
msgid "You can obtain a provided compose file `here <https://raw.githubusercontent.com/Nitrokey/nethsm/refs/heads/main/src/container/alpine/compose-unix.yaml>`__. Make sure you have the necessary files for the secrets, mentioned in the compose file, available."
msgid "To run the container without the compose file you need to provide an external etcd yourself. `Here <https://quay.io/coreos/etcd>`__ you find the recommended container image for etcd. Make sure to pass the configuration options, as described in chapter `Configuration <production-image.html#Configuration>`__."
msgid "The container uses a self-signed TLS certificate. Make sure to use the correct connection settings to establish a connection. Please refer to chapter `NetHSM introduction <index.html>`__ to learn more."
msgid "You can obtain a provided compose file `here <https://raw.githubusercontent.com/Nitrokey/nethsm/refs/heads/main/src/container/alpine/compose-unikernel.yaml>`__. Make sure you have the necessary files for the secrets, mentioned in the compose file, available."
msgid "This will run NetHSM as a unikernel inside a KVM virtual machine. The container will expose the REST API, via the HTTPS protocol, on the interface `tap200` with the IP address `192.168.1.100` and port `8443`."
0 commit comments