exec user process caused

Following the production deployment guide for docker without nginx I executed the following commands

git clone https://github.com/mattermost/docker
cd docker
cp env.example .env
mkdir -p ./volumes/app/mattermost/{config,data,logs,plugins,client/plugins,bleve-indexes}
sudo chown -R 2000:2000 ./volumes/app/mattermost
sudo docker-compose -f docker-compose.yml -f docker-compose.without-nginx.yml up -d

and found the docker image restarting because of this error (using the docker logs command)

standard_init_linux.go:228: exec user process caused: operation not permitted
standard_init_linux.go:228: exec user process caused: operation not permitted
standard_init_linux.go:228: exec user process caused: operation not permitted
standard_init_linux.go:228: exec user process caused: operation not permitted
standard_init_linux.go:228: exec user process caused: operation not permitted
standard_init_linux.go:228: exec user process caused: operation not permitted
standard_init_linux.go:228: exec user process caused: operation not permitted
standard_init_linux.go:228: exec user process caused: operation not permitted
standard_init_linux.go:228: exec user process caused: operation not permitted

a quick search online says this might be related to an error with an init script for the pod?

Start with the production deployment guide and the docker-compose.yml and docker-compose.without-nginx.yml files used in the report. Reproduce the deployment and inspect the container logs and the image's init script entry point to determine why the process cannot be executed. Done means identifying the cause and documenting or fixing the deployment so the image starts successfully.