Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Operation Not Permitted #128

Open
Itschotsch opened this issue May 17, 2023 · 6 comments · May be fixed by #135
Open

Operation Not Permitted #128

Itschotsch opened this issue May 17, 2023 · 6 comments · May be fixed by #135

Comments

@Itschotsch
Copy link

Itschotsch commented May 17, 2023

I'm on Ubuntu 22.10, with docker-compose 1.29.2 and Docker 20.10.21, both installed using apt (not snap), on a DigitalOcean server.
I followed the installation instructions at https://docs.mattermost.com/install/install-docker.html exactly.

  • For step 4, I copied a fullchain.pem and privkey.pem I already had for the same domain to the specified directory with tthe respective names.
  • I skipped the optional step 5.
  • For step 6, I deployed using the included NGINX.
    After running sudo docker-compose -f docker-compose.yml -f docker-compose.nginx.yml up (not detached to see the output), I get:
Creating network "mattermost" with the default driver
Creating docker_postgres_1 ... done
Creating docker_mattermost_1 ... done
Creating nginx_mattermost    ... done
Attaching to docker_postgres_1, docker_mattermost_1, nginx_mattermost
mattermost_1  | exec /entrypoint.sh: operation not permitted
postgres_1    | exec /usr/local/bin/docker-entrypoint.sh: operation not permitted
nginx_mattermost | exec /docker-entrypoint.sh: operation not permitted
docker_mattermost_1 exited with code 1
docker_postgres_1 exited with code 1

I restarted the server without any other containers running (ports were free), I tried step 6 without the included NGINX, I ran sudo chmod 777 -R ., I ran everything as root, I searched the web, nothing worked. Is this a bug? Did I do everything correctly? What can I do to make this work?

@ZelnickB
Copy link

ZelnickB commented Jul 28, 2023

Same issue here when installing without the included NGINX. @Itschotsch, did you find a fix?

@Itschotsch
Copy link
Author

@ZelnickB Sadly not, I never managed to install it. :( I really hope they look at this soon!

@ZelnickB
Copy link

ZelnickB commented Jul 31, 2023

I think that I found the problem. Commenting the lines

security_opt:
    - no-new-privileges:true

out of the /docker-compose.yml file (for both services) seems to solve the issue.

I'll open up a PR.

ZelnickB added a commit to ZelnickB/fork.mattermost_docker that referenced this issue Aug 2, 2023
This commit removes the no-new-privileges security options from the services defined in the /docker-compose.yml file, as it causes errors when attempting to start the containers (see mattermost#128). Removing the security option seems to resolve the problem.
@Itschotsch
Copy link
Author

@ZelnickB I can confirm this now works for me too. Thanks!

@LeNguyenGiaBao
Copy link

@ZelnickB I have commented the line "- no-new-privileges:true" but the error is also exist. I find the answer here from @yosifkit. The config now is

security_opt:
#   - no-new-privileges:true
  - seccomp:unconfined

for both mattermost and postgresdb

@ZelnickB
Copy link

ZelnickB commented May 9, 2024

@LeNguyenGiaBao Weird—it worked for me when I tried it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants