Remove the sub-command in the container guide

docs/guides/src/main/server/containers.adoc

@@ -42,14 +42,14 @@ ENV KC_DB_URL=<DBURL>
 ENV KC_DB_USERNAME=<DBUSERNAME>
 ENV KC_DB_PASSWORD=<DBPASSWORD>
 ENV KC_HOSTNAME=localhost
-ENTRYPOINT ["/opt/keycloak/bin/kc.sh", "start"]
+ENTRYPOINT ["/opt/keycloak/bin/kc.sh"]
 ----
 The build process includes multiple stages:
 
 * The `build` command applies options and includes custom providers to create an optimized image.
 * The files generated by the `build` stage are copied into a new image.
 * In this runner image, the specific run configuration is applied. That configuration contains a keystore, the environment-specific hostname configuration, and database configuration.
-* In the entrypoint, the `start` command starts the image in production mode.
+* In the entrypoint, the `kc.sh` enable access to all the distribution sub-commands.
 
 This example uses a multi-staged build to demonstrate the build and run steps.  However, you can also build a single-staged docker image by removing the following two lines:
 
@@ -71,7 +71,10 @@ podman|docker build . -t prebuilt_keycloak
 To start the image, run:
 [source, bash]
 ----
-podman|docker run --name optimized_keycloak -p 8443:8443 -e KEYCLOAK_ADMIN=admin -e KEYCLOAK_ADMIN_PASSWORD=change_me prebuilt_keycloak
+podman|docker run --name optimized_keycloak -p 8443:8443 \
+        -e KEYCLOAK_ADMIN=admin -e KEYCLOAK_ADMIN_PASSWORD=change_me \
+        prebuilt_keycloak \
+        start
 ----
 Keycloak starts in production mode, using only secured HTTPS communication, and is available on `https://localhost:8443`.
 Notice that the startup log contains the following line: