Skip to content

Commit 6f89931

Browse files
Update Troubleshooting.md to include more information around cgroup. (#145)
1 parent a45f96f commit 6f89931

File tree

1 file changed

+14
-0
lines changed

1 file changed

+14
-0
lines changed

docs/Troubleshooting.md

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -25,6 +25,20 @@ sudo update-initramfs -c -k all
2525

2626
They will take a while to run (about 10 minutes), but once complete reboot your machine and delete any created containers that velong to the ce_dev image. When you rebuild the ce-dev controller (by running any command) it should create fine.
2727

28+
### Cgroup On Older Projects
29+
30+
ce-dev does allow for the use of Cgroup 2, but some older projects will need upgrading to allow this to work. This means that the ce-dev controller will work fine, but some projects may fail to start some containers. This error will become apparent if you see the "unreachable" error when running the `ce-dev provision` step.
31+
32+
If this is the case then make sure that the cgroup option is set in your ce-dev.compose.prebuilt.yml file for the services that aren't starting.
33+
34+
```
35+
services:
36+
web:
37+
cgroup: host
38+
image: 'codeenigma/drupal9-web:latest'
39+
expose:
40+
```
41+
2842
## VM Networking issue
2943
If you're running ce-dev from within a Virtual Machine (eg. KVM/qemu), Docker container network ports are only 'exposed' to the hypervisor (ie the VM), and are not published for external access.
3044
In order to access sites/files deployed by ce-dev, the ports needs to be published so that the Docker containers can be accessed from your workstation.

0 commit comments

Comments
 (0)