# Container

## Prepare

Begin by obtaining authentication credentials from your Fortified ID representative. Use the credentials to log in to the FortifiedID Docker Registry by any available method, [see here for instructions on Unix/Linux and Windows](https://docs.docker.com/engine/reference/commandline/login/).

Example for Unix/Linux:

Transfer the token from `customer_access_credentials.json` to `password.txt`:

1. Open the `customer_access_credentials.json` file that you have received.
2. Locate and copy the access\_token value.
3. Open or create the `password.txt file`.
4. Paste the access\_token value into `password.txt`.
5. Replace `<username>` with your username that you have received in the following command and execute it.

```
cat ./password.txt | docker login fortifiedid.jfrog.io --username <username> --password-stdin
```

Depending on your system configuration, you may need to run the logon command with different user rights, such as the `root` user and the current user account.&#x20;

## Verify

To verify the Docker setup, run the server:

Replace \<container\_display\_name> with the container name and replace \<product\_name>:\<version> with the image product name and version.

```
docker run --detach --name <container_display_name> fortifiedid.jfrog.io/docker/fortifiedid/<product_name>:<version> -c Node config/config.json
```

Parameter explanation:

<table><thead><tr><th width="317"></th><th></th><th data-hidden></th><th data-hidden></th></tr></thead><tbody><tr><td><code>-c</code></td><td>Direct system output to <code>stdout</code>. </td><td></td><td></td></tr><tr><td><code>Node</code></td><td>Start the <code>Node</code> module.</td><td></td><td></td></tr><tr><td><code>config/config.json</code></td><td>Use the given configuration file. Path is relative to <code>SERVER_HOME</code> inside the container.</td><td></td><td></td></tr></tbody></table>

Check the log to ensure that the server was successfully bootstrapped:

```
docker logs -f <container_display_name>
```

{% hint style="warning" %}
Using "RC releases"?! Note that only last 5 are stored and are frequently replaced with new and cannot be regenerated.
{% endhint %}