[WIP] Running BOSH and CF with Docker

[beyhan]

To try this you will need:

1. A directory setup like:

|- bosh-deployment //with the fork from https://github.com/beyhan/bosh-deployment/tree/docker-create-env
|- cf-deployment //with the fork from https://github.com/beyhan/cf-deployment/tree/docker-create-env
|- bosh-local //an empty directory which could be called also differently

2. Change the Docker Desktop configuration to use cgroups v1 by applying the solution described in https://stackoverflow.com/questions/74345772/is-it-possible-to-downgrade-to-cgroup-v1-for-docker-desktop-on-osx

3. If not the case I would recommend to increase the Docker resource usage to a memory limit of 10GB and Swap to 3GB which worked fine on machine with 16GB RAM. CPU doesn't seem to be of an issue but I had a limit of 14.

4. In bosh-local execute ./../bosh-deployment/docker/create-env.sh

Troubleshooting:
If bosh ssh doesn't work you could SSH into a container with docker container exec -it <containerID> /bin/bash. To identify the container belonging to an instance group use bosh vms to get the VM CID which is added as container Name in Docker, so that with docker ps -a | grep <VM-CID> you can find the right one.

Current issues:
The deployment of CF is failing because of an issue with diego-cell:

{"timestamp":"2024-12-12T08:27:22.095699191Z","level":"error","source":"grootfs","message":"grootfs.init-store.store-manager-init-store.overlayxfs-init-filesystem.mounting-fs-failed","data":{"allOpts":"loop,pquota,noatime","destination":"/var/vcap/data/grootfs/store/unprivileged","error":"exit status 32","filesystemPath":"/var/vcap/data/grootfs/store/unprivileged.backing-store","session":"1.1.2","source":"/var/vcap/data/grootfs/store/unprivileged.backing-store","spec":{"UIDMappings":[{"HostID":4294967294,"NamespaceID":0,"Size":1},{"HostID":1,"NamespaceID":1,"Size":4294967293}],"GIDMappings":[{"HostID":4294967294,"NamespaceID":0,"Size":1},{"HostID":1,"NamespaceID":1,"Size":4294967293}],"StoreSizeBytes":19777536000},"storePath":"/var/vcap/data/grootfs/store/unprivileged"}}
{"timestamp":"2024-12-12T08:27:22.095844104Z","level":"error","source":"grootfs","message":"grootfs.init-store.store-manager-init-store.initializing-filesystem-failed","data":{"backingstoreFile":"/var/vcap/data/grootfs/store/unprivileged.backing-store","error":"Mounting filesystem: exit status 32: mount: /var/vcap/data/grootfs/store/unprivileged: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error.\n","session":"1.1","spec":{"UIDMappings":[{"HostID":4294967294,"NamespaceID":0,"Size":1},{"HostID":1,"NamespaceID":1,"Size":4294967293}],"GIDMappings":[{"HostID":4294967294,"NamespaceID":0,"Size":1},{"HostID":1,"NamespaceID":1,"Size":4294967293}],"StoreSizeBytes":19777536000},"storePath":"/var/vcap/data/grootfs/store/unprivileged"}}
{"timestamp":"2024-12-12T08:27:22.095882736Z","level":"error","source":"grootfs","message":"grootfs.init-store.init-store-failed","data":{"error":"initializing filesyztem: Mounting filesystem: exit status 32: mount: /var/vcap/data/grootfs/store/unprivileged: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error.\n","session":"1"}}

[beyhan]

I found the reason for cloudfoundry/bosh-docker-cpi-release#18 during this experiment.