first try on photon-os for docker-swarm fails with cgroup
Describe the bug
Having fresh install on photon-os giving it a try as I use VMware and usually use Ubuntu/Debian, I wanted to give photon a try for use with docker/swarm.
I've had several fresh installs of photon and tried to setup swarm-pit for master/management like (see reproduction steps).
Each time swarmpit install fails to deploy and on console-log of vmware-guest running photon there is this error -- no matter I give the VM-Guest 2 GB of RAM or 8 GB:
cgroup out of memory: killed
Reproduction steps
- docker swarm init
- docker run -it --rm
--name swarmpit-installer
--volume /var/run/docker.sock:/var/run/docker.sock
swarmpit/install:1.9
Starting swarmpit.......................FAILED! Swarmpit is not responding for a long time. Aborting installation...:( Please check logs and cluster status for details. ...
Expected behavior
swarmpit should run
Additional context
cat /etc/os-release NAME="VMware Photon OS" VERSION="4.0"
docker version Client: Docker Engine - Community Version: 24.0.5 API version: 1.43 Go version: go1.20.12 Git commit: ced0996 Built: Thu Dec 21 03:16:59 2023 OS/Arch: linux/amd64 Context: default
Server: Docker Engine - Community
Engine:
Version: 24.0.5
API version: 1.43 (minimum version 1.12)
Go version: go1.20.12
Git commit: a61e2b4
Built: Thu Dec 21 03:18:08 2023
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.6.8
GitCommit: 9cd3357b7fd7218e4aec3eae239db1f68a5a6ec6
runc:
Version: 1.1.12
GitCommit:
docker-init:
Version: 0.19.0
GitCommit: de40ad0
I've additionally addressed the bug to swarmpit, because I'm not shure if this is a photon-os or swarm-pit specific issue: https://github.com/swarmpit/swarmpit/issues/684
I've tried now on good old ubuntu/debian and in both cases it's working also with 2GB of RAM. Seems to be kind of photon-os/cgroup issue that should be discussed.
@prashant1221
Added a workaround description on https://github.com/swarmpit/swarmpit/issues/684. Accordingly to https://github.com/swarmpit/swarmpit/issues/643, the issue happens on fedora as well.