Getting Started: Add information on Docker exit code 100

see photoprism/photoprism#4819

docs/getting-started/faq.md

@@ -265,15 +265,15 @@ Please be aware, though, that we do not have the resources to provide support an
 
 ### What can I do if the Docker container fails to start with exit code 100?
 
-A startup error similar to the following indicates that you are [using a custom service configuration](https://github.com/photoprism/photoprism/discussions/4819) that is incompatible with our [Docker images](docker-compose.md):
+A container startup error similar to the following indicates that you are [using a custom service configuration](https://github.com/photoprism/photoprism/discussions/4819) that is incompatible with our [Docker images](docker-compose.md):
 
 ```
 /package/admin/s6-overlay/libexec/preinit:
 fatal: /run belongs to uid 0 instead of 100
 and we're lacking the privileges to fix it.
 ```
 
-In particular, this can happen if you have specified an unsupported user or group ID through the optional [`user`](https://docs.docker.com/reference/compose-file/services/#user) property in your [`compose.yaml`](https://dl.photoprism.app/docker/compose.yaml) file to run the service, and at the same time set [`no-new-privileges:true`](https://github.com/just-containers/s6-overlay/issues/552#issuecomment-2339563938) in the [`security_opt`](https://docs.docker.com/reference/compose-file/services/#security_opt) section.
+In particular, this can happen if you have specified an *unsupported* user or group ID through the optional [`user`](https://docs.docker.com/reference/compose-file/services/#user) property in your [`compose.yaml`](https://dl.photoprism.app/docker/compose.yaml) file to run the service, and at the same time set [`no-new-privileges:true`](https://github.com/just-containers/s6-overlay/issues/552#issuecomment-2339563938) in the [`security_opt`](https://docs.docker.com/reference/compose-file/services/#security_opt) section.
 
 Please also check if you have specified *both* a [`user`](https://docs.docker.com/reference/compose-file/services/#user) service property and these [`environment`](https://docs.docker.com/reference/compose-file/services/#environment) variables to specify the user and/or group ID under which the service should run, as this is neither required nor recommended:
 
@@ -292,8 +292,8 @@ The supported ID ranges for running our container images are as follows:
 
 [Learn more ›](https://docs.photoprism.app/getting-started/config-options/#docker-image)
 
-!!! tip ""
-    If you are experiencing a similar problem with a custom configuration that we did not provide or recommend, please try changing it to see if that helps before asking our team or community members for support. 🛟
+!!! info ""
+    If you are experiencing a similar problem with a custom configuration that we did not provide or recommend, please try changing it to see if that helps before [asking our team](https://www.photoprism.app/kb/getting-support) or [community members](https://github.com/photoprism/photoprism/discussions) for support. 🛟
 
 ### Why does your Docker image use the Plus License instead of the AGPL?
 

docs/getting-started/troubleshooting/docker.md

@@ -115,17 +115,17 @@ of your `compose.yaml` or `docker-compose.yml`.
 
 ### Start Fails with Exit Code 100
 
-A startup error similar to the following indicates that you are [using a custom service configuration](https://github.com/photoprism/photoprism/discussions/4819) that is incompatible with our [Docker images](../docker-compose.md):
+A container startup error similar to the following indicates that you are [using a custom service configuration](https://github.com/photoprism/photoprism/discussions/4819) that is incompatible with our [Docker images](../docker-compose.md):
 
 ```
 /package/admin/s6-overlay/libexec/preinit:
 fatal: /run belongs to uid 0 instead of 100
 and we're lacking the privileges to fix it.
 ```
 
-In particular, this can happen if you have specified an unsupported user or group ID through the optional [`user`](https://docs.docker.com/reference/compose-file/services/#user) property in your [`compose.yaml`](https://dl.photoprism.app/docker/compose.yaml) file to run the service, and at the same time set [`no-new-privileges:true`](https://github.com/just-containers/s6-overlay/issues/552#issuecomment-2339563938) in the [`security_opt`](https://docs.docker.com/reference/compose-file/services/#security_opt) section.
+In particular, this can happen if you have specified an *unsupported* user or group ID through the optional [`user`](https://docs.docker.com/reference/compose-file/services/#user) property in your [`compose.yaml`](https://dl.photoprism.app/docker/compose.yaml) file to run the service, and at the same time set [`no-new-privileges:true`](https://github.com/just-containers/s6-overlay/issues/552#issuecomment-2339563938) in the [`security_opt`](https://docs.docker.com/reference/compose-file/services/#security_opt) section.
 
-Please also check if you have specified both a [`user`](https://docs.docker.com/reference/compose-file/services/#user) service property and these [`environment`](https://docs.docker.com/reference/compose-file/services/#environment) variables to specify the user and/or group ID under which the service should run, as this is neither required nor recommended:
+Please also check if you have specified *both* a [`user`](https://docs.docker.com/reference/compose-file/services/#user) service property and these [`environment`](https://docs.docker.com/reference/compose-file/services/#environment) variables to specify the user and/or group ID under which the service should run, as this is neither required nor recommended:
 
 ```yaml
 services:
@@ -142,8 +142,8 @@ The supported ID ranges for running our container images are as follows:
 
 [Learn more ›](https://docs.photoprism.app/getting-started/config-options/#docker-image)
 
-!!! tip ""
-    If you are experiencing a similar problem with a custom configuration that we did not provide or recommend, please try changing it to see if that helps before asking our team or community members for support. 🛟
+!!! info ""
+    If you are experiencing a similar problem with a custom configuration that we did not provide or recommend, please try changing it to see if that helps before [asking our team](https://www.photoprism.app/kb/getting-support) or [community members](https://github.com/photoprism/photoprism/discussions) for support. 🛟
 
 ### IPTables Firewall