Portainer Docker Containers For WHMCS - Revision history

Karolina at 11:33, 1 April 2026

2026-04-01T11:33:47Z

Karolina: /* Running Docker-in-Docker (DinD) */

2026-03-16T10:58:27Z

‎Running Docker-in-Docker (DinD)

Karolina: /* Docker-in-Docker Workflow */

2026-03-16T10:35:20Z

‎Docker-in-Docker Workflow

Karolina: /* Configuration of Server */

2026-03-16T10:33:34Z

‎Configuration of Server

Karolina: /* About Portainer Docker Containers For WHMCS */

2026-03-16T10:32:51Z

‎About Portainer Docker Containers For WHMCS

Karolina: /* Improving Container Security Using Alternative Runtimes */

2026-03-16T10:30:36Z

‎Improving Container Security Using Alternative Runtimes

Karolina: /* Improving Container Security Using Alternative Runtimes */

2026-03-16T10:29:34Z

‎Improving Container Security Using Alternative Runtimes

Karolina: /* Improving Container Security Using Alternative Runtimes */

2026-03-16T10:28:55Z

‎Improving Container Security Using Alternative Runtimes

Karolina: /* Docker-in-Docker Workflow */

2026-03-16T10:26:42Z

‎Docker-in-Docker Workflow

Karolina: /* Configuration of Server */

2026-03-16T10:23:52Z

‎Configuration of Server

@@ Line 1: / Line 1: @@
 <meta name="keywords" content="portainer docker containers for whmcs, whmcs portainer docker containers configuration, whmcs portainer docker containers management, whmcs portainer docker containers installation, whmcs portainer docker containers common problems, about whmcs portainer docker containers, whmcs sportainer docker containers documentation, whmcs portainer docker containers faq, whmcs portainer docker containers help, whmcs sportainer docker containers guide, whmcs portainer docker containers wiki, whmcs portainer docker containers tutorial, whmcs portainer docker containers tips"></meta>
 <meta name="description" content="ModulesGarden Wiki Contains All The Information You Need About The Portainer Docker Containers For WHMCS Module."></meta>
 =About [https://www.modulesgarden.com/products/whmcs/portainer-docker-containers Portainer Docker Containers For WHMCS]=

@@ Line 1,466: / Line 1,466: @@
 ====Running Docker-in-Docker (DinD)====
 {|
-|style="padding: 10px 0px 15px 15px;"|Docker-in-Docker (DinD) is a setup where a container runs its own Docker daemon, allowing it to build and run additional containers inside it.<br/>
+|style="padding: 10px 0px 20px 15px;"|Docker-in-Docker (DinD) is a setup where a container runs its own Docker daemon, allowing it to build and run additional containers inside it.
-This can be useful for workloads such as:
-* CI/CD pipelines that build Docker images
-* development environments requiring Docker inside the container
-* testing containerized applications
 |}
 {|

@@ Line 702: / Line 702: @@
 |}
 {| class="wikitable" style="border-left:6px solid #e67e22; background:#fff6ec; margin:10px 10px;"
-|style="padding:20px;"|
+|style="padding:12px;"|
 '''⚠ Important – Portainer Node Registration'''
@@ Line 709: / Line 709: @@
 |}
 {|
-|style="padding: 0px 0px 15px 15px;"|'''Technical Notes:''' <br/>
+|style="padding: 10px 0px 15px 15px;"|'''Technical Notes:''' <br/>
 The DinD container extends the official <code>docker:dind</code> image by including the '''Portainer Agent'''.<br/>
 Example image configuration:
@@ Line 727: / Line 727: @@
 |}
 {| class="wikitable" style="border-left:6px solid #c0392b; background:#fdecea; margin:10px 10px;"
-|style="padding:20px;"|
+|style="padding:12px;"|
 '''🔐 Security Notes – Docker-in-Docker'''
@@ Line 737: / Line 737: @@
 |}
 {|
-|style="padding: 0px 0px 15px 15px;"|'''Recommended Reading:'''
+|style="padding: 10px 0px 15px 15px;"|'''Recommended Reading:'''
 * [https://docs.docker.com/engine/security/protect-access/ Docker Docs: Protect the Docker Daemon Socket]
 * [https://cheatsheetseries.owasp.org/cheatsheets/Docker_Security_Cheat_Sheet.html OWASP Docker Security Cheat Sheet]

@@ Line 445: / Line 445: @@
 |}
 {| class="wikitable" style="border-left:6px solid #e67e22; background:#fff6ec; margin:10px 10px;"
-|style="padding:20px;"|
+|style="padding:12px;"|
 '''⚠ Important – Infrastructure Security Notice'''
@@ Line 454: / Line 454: @@
 |}
 {|
-|style="padding: 0px 0px 15px 15px;"|
+|style="padding: 10px 0px 15px 15px;"|
 '''10. Fill in the ''Name'', provide the ''Hostname'' or ''IP Address'' in both fields at the top ''(filling in both Hostname and IP Address fields is required to proceed)''. '''<br/>
 In the '''Server Details''' section:

@@ Line 47: / Line 47: @@
 {| class="wikitable" style="border-left:6px solid #c0392b; background:#fdecea; margin:10px 10px;"
-|style="padding:20px;"|
+|style="padding:12px;"|
 '''⚠ Privileged Containers Warning'''

@@ Line 1,439: / Line 1,439: @@
 |}
 {|
-|style="padding: 0px 0px 10px 15px;"|'''Example: Using Sysbox Runtime'''<br/>
+|style="padding: 0px 0px 30px 15px;"|'''Example: Using Sysbox Runtime'''<br/>
 One example of an alternative runtime is '''[https://github.com/nestybox/sysbox Sysbox]''', which provides stronger container isolation and allows running system-level software inside containers.<br/>
 Sysbox improves container isolation by:
@@ Line 1,451: / Line 1,451: @@
 * Kubernetes / K3s
 * buildx (including multi-architecture builds)
-|}
-{| class="wikitable" style="border-left:6px solid #f39c12; background:#fff8e5; margin:0px 10px;"
+{| class="wikitable" style="border-left:6px solid #f39c12; background:#fff8e5; margin:10px 10px;"
-|style="padding:30px;"|
+|style="padding:12px;"|
 '''⚠ Important Notes – Alternative Container Runtimes'''
@@ Line 1,461: / Line 1,461: @@
 For more details on configuring alternative runtimes in Docker, please refer to the
 [https://docs.docker.com/engine/daemon/alternative-runtimes/ official Docker documentation].
 |}

@@ Line 1,452: / Line 1,452: @@
 * buildx (including multi-architecture builds)
 |}
-{|
+{| class="wikitable" style="border-left:6px solid #f39c12; background:#fff8e5; margin:10px 10px;"
-|style="padding: 0px 0px 30px 15px;"|
+|style="padding:20px;"|
-'''Important Notes:'''
+'''⚠ Important Notes – Alternative Container Runtimes'''
-# Sysbox is a third-party container runtime and must be installed separately on the Docker host before it can be used.
-# Alternative runtimes must be installed and available on the Docker host. If the selected runtime is not supported by the Docker node, container deployment may fail.
+* '''Sysbox''' is a third-party container runtime and must be installed separately on the Docker host before it can be used.
-'''For more details on configuring alternative runtimes in Docker''', please refer to the [https://docs.docker.com/engine/daemon/alternative-runtimes/ official documentation].
+* Alternative runtimes must be installed and available on the Docker host. If the selected runtime is not supported by the Docker node, container deployment may fail.
 |}
 ====Running Docker-in-Docker (DinD)====
 {|

@@ Line 700: / Line 700: @@
 ** During '''Terminate''', both the DinD container and its Portainer node are deleted.
 ** '''Suspend''' and '''Unsuspend''' actions remain unaffected.<br/>
-'''''Important:''' The created Docker-in-Docker container is registered as a new Portainer node. Make sure your Portainer license allows for adding additional nodes without limitation.''
+The created Docker-in-Docker container is automatically registered as a new node in Portainer.
 |}
 {|
@@ Line 721: / Line 726: @@
 * Other ports - dynamically assigned for client applications
 |}
-{|
+{| class="wikitable" style="border-left:6px solid #c0392b; background:#fdecea; margin:10px 10px;"
-|style="padding: 0px 0px 15px 15px;"|'''Security Notes:''' <br/>
+|style="padding:20px;"|
-The module does not modify or manage the Docker configuration on your server. All aspects of host and container security remain the responsibility of the server administrator.<br/>
+'''🔐 Security Notes – Docker-in-Docker'''
-Running Docker-in-Docker requires '''privileged containers''' and can expose the Docker API internally.<br/>
-For secure deployments, always use TLS when exposing the Docker API and follow official security guidelines.
+The module does '''not''' modify or manage the Docker configuration on your server. All aspects of host and container security remain the responsibility of the server administrator.
 |}
 {|