-
Notifications
You must be signed in to change notification settings - Fork 213
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
Comments
Same issue here when installing without the included NGINX. @Itschotsch, did you find a fix? |
@ZelnickB Sadly not, I never managed to install it. :( I really hope they look at this soon! |
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. |
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.
@ZelnickB I can confirm this now works for me too. Thanks! |
@LeNguyenGiaBao Weird—it worked for me when I tried it. |
I am not able to reproduce the issue on an Ubuntu 22.04.5 machine, using Docker |
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.
After running
sudo docker-compose -f docker-compose.yml -f docker-compose.nginx.yml up
(not detached to see the output), I get: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?The text was updated successfully, but these errors were encountered: