Hi Marijn,
Thanks for your question. You are right, we are still upgrading our documentation. Your issue is not covered yet, but we try to provide a solution for you. Most of the steps require root permissions:
- Boot up a fresh Cloudogu EcoSystem, but do not start the setup yet
- Change the IP range of the Docker default network interface (
docker network inspect bridge
for details)- Create the file
/etc/ces/daemon.json
with the following content:
- Create the file
{
"bip": "192.168.178.2/24"
}
Note: The subnet you wanted to use (10.17.0.0/16) did not work out in our tests. Maybe this was due to our network environment, which is probably different from yours. “192.168.178.2/24” however did work out.
- Restart the Docker daemon via
systemctl restart docker
- Check the Docker daemon status via
systemctl status docker
. There should be no “failed” or “error” messages.
- Change the IP range of the “cesnet1” docker network (
docker network inspect cesnet1
for details)- Remove the network via
docker network rm cesnet1
- Recreate the network with your IP range:
docker network create --subnet=10.18.0.0/16 --ip-range=10.18.0.0/24 cesnet1
- Add a new firewall rule for the new IP range:
ufw allow from "$(docker network inspect cesnet1 -f '{{(index .IPAM.Config 0).Subnet}}')" to any port 4001
- Remove the old firewall rule:
ufw delete 5
- This will delete the rule “allow from 172.18.0.0/16 to any port 4001”
- Confirm with “y”
- Remove the network via
Now you should be good to go and can continue with the regular setup in your browser.
If you have any more questions, please feel free to ask!
For your interest: We plan to offer a dedicated VMware image in the near future to ease the use of the CES.
Kind regards