PermissionError: [Errno 13] Permission denied: '/manage.py'

Question:

I am trying to run the following command in docker-composer, to start project with django-admin:

docker-compose run app sh -c "django-admin startproject app ."

This produces the error:

    Traceback (most recent call last):
  File "/usr/local/bin/django-admin", line 10, in <module>
    sys.exit(execute_from_command_line())
  File "/usr/local/lib/python3.7/site-packages/django/core/management/__init__.py", line 381, in execute_from_command_line
    utility.execute()
  File "/usr/local/lib/python3.7/site-packages/django/core/management/__init__.py", line 375, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/usr/local/lib/python3.7/site-packages/django/core/management/base.py", line 323, in run_from_argv
    self.execute(*args, **cmd_options)
  File "/usr/local/lib/python3.7/site-packages/django/core/management/base.py", line 364, in execute
    output = self.handle(*args, **options)
  File "/usr/local/lib/python3.7/site-packages/django/core/management/commands/startproject.py", line 20, in handle
    super().handle('project', project_name, target, **options)
  File "/usr/local/lib/python3.7/site-packages/django/core/management/templates.py", line 155, in handle
    with open(new_path, 'w', encoding='utf-8') as new_file:
PermissionError: [Errno 13] Permission denied: '/manage.py'

The Dockerfile is as follows:

FROM python:3.7-alpine
MAINTAINER anubrij chandra

ENV PYTHONUNBUFFERED 1

COPY ./requirements.txt /requirements.txt

RUN pip install -r /requirements.txt

RUN mkdir /app
COPY ./app /app



RUN adduser -D dockuser
USER dockuser

My docker-compose.yml:

version: "3"

services:
  app:
    build:
      context: .
    ports:
      - "8000:8000"
    volumes:
      - ./app:/app
    command: >
      sh -c "python manage.py runserver 0.0.0.0:8000"

I applied the solution suggested in this Stack Overflow thread, but it didn’t work.

I’m using Ubuntu 18.04.

Asked By: Anubrij Chandra

||

Answers:

add this to your Dockerfile after RUN adduser -D dockuser:

RUN chown dockuser:dockuser -R /app/

and why you COPYthe files if you already mount them ?

if you want to keep the mount , you need to add rw persmission on the folder on the HOST system not on the Container

Answered By: LinPy

In your dockerfile, you are pointing to a new user dockuser.

RUN adduser -D dockuser
USER dockuser

Hence your container will start with user dockuser which does not seem to have proper permissions to run /manage.py.

You can either

  • remove the above mentioned lines where you create and point to
    dockuser.

OR

  • provide appropriate permissions to user dockuser using chown and chmod commands in your dockerfile for /manage.py file.

I have answered such similar question here.

Answered By: mchawre

If you’re on mac this might work for you.

After 4 days of troubleshooting this error (and other strange errors) I found out that I needed to fix dockers permissions in my file system. To do this go to:

System Preferences -> Security & Privacy -> Privacy tab -> Full Disk Access (on the left, somewhere in the list) -> Click on the + -> Docker application

Terribly frustrating problem to debug, hope it helps.

Answered By: Toms Code

ubuntu 21.04

I got here searching for PermissionError: [Errno 13] Permission denied: so i’ll just leave this here.

note: the below answer doesn’t work for multi user systems … see this answer instead for another possible solution


If you want to set it and forget it for 1 user, your own user … here’s what I have on my dev machine.

I didn’t own the unix socket, so I chowned it. ( this got it working straight away )

sudo chown $(whoami):$(whoami) /var/run/docker.sock

Another, more permanent solution for your dev environment, is to modify the user ownership of the unix socket creation. This will give your user the ownership, so it’ll stick between restarts:

sudo nano /etc/systemd/system/sockets.target.wants/docker.socket

docker.socket:

[Unit]
Description=Docker Socket for the API

[Socket]
ListenStream=/var/run/docker.sock
SocketMode=0660
SocketUser=YOUR_USERNAME_HERE
SocketGroup=docker

[Install]
WantedBy=sockets.target

Again another less hacky solution: https://stackoverflow.com/a/70124863/2026508

Answered By: jmunsch

I had the same issue and solved it by adding my user to the docker group:

$ sudo usermod -aG docker $(whoami)
Answered By: wvdgoot

The Dockerfile that I was using was in the shared directory of my virtual machine (VirtualBox). Therefore, my issue was related to the default permission of this directory (UID=root, GID=vboxdf). I had to change it to my current user to properly run my container.

See https://superuser.com/a/640028/1655184 for a description on how to change the owner.

Answered By: Ling

For me it was a WSL2 / Docker-Desktop setup issue on Windows.

What was missing was to explicitly enable the WSL distro: Docker Desktp Settings > Resources > WSL Integration > enable your distro

Then re-open WSL shell.

Before I could not even do docker run hello-world but also had a very similar error message as the OP when running docker-compose.

Answered By: Tom

adding path to app like ‘/home/user/app:/app’ in docker-compose instead of just ‘.:/app’ resolved my problem

For ubuntu, just add sudo to your command and run as root to get the permissions.

sudo docker-compose run app sh -c "django-admin startproject app ."

Answered By: Solomon Botchway