Laravel & Docker: The stream or file "/var/www/html/storage/logs/laravel.log" could not be opened: failed to open stream: Permission denied

Question

This is my folder structure:

+-- root-app-dir
|   +-- docker
|   |   +-- Dockerfile
|   |   +-- nginx.conf
|   +-- src // this is where the Laravel app lives
|   +-- docker-compose.yml

This is my docker-compose.yml

version: '2'

services:
  app:
    build:
      context: ./docker
      dockerfile: Dockerfile
    image: lykos/laravel
    volumes:
      - ./src/:/var/www/html/
    networks:
      - app-network

  nginx:
    image: nginx:latest
    volumes:
      - ./src/:/var/www/html/
      - ./docker/nginx.conf:/etc/nginx/conf.d/default.conf
    ports:
      - 8000:80
    networks:
      - app-network

  mysql:
    image: mysql:5.7
    ports: 
      - "4306:3306"
    environment:
      MYSQL_DATABASE: homestead
      MYSQL_USER: homestead
      MYSQL_PASSWORD: secret
      MYSQL_ROOT_PASSWORD: secret
    volumes:
      - mysqldata:/var/lib/mysql
    networks:
      - app-network

  phpmyadmin:
    image: phpmyadmin/phpmyadmin
    ports:
      - 8080:80
    links:
      - mysql
    environment:
      PMA_HOST: mysql

volumes:
  mysqldata:
    driver: "local"

networks:
  app-network:
    driver: "bridge"

This is my nginx.conf

server {
  root /var/www/html/public;

  index index.html index.htm index.php;

  server_name _;
  charset utf-8;

  location = /favicon.ico { log_not_found off; access_log off; }
  location = /robots.txt { log_not_found off; access_log off; }

  location / {
    try_files $uri $uri/ /index.php$is_args$args;
  }

  location ~ \.php$ {
    # include snippets/fastcgi-php.conf;
    include fastcgi_params;
    fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
    fastcgi_param PATH_INFO $fastcgi_path_info;
    fastcgi_pass app:9000;
    fastcgi_index index.php;
  }

  error_page 404 /index.php;

  location ~ /\.ht {
    deny all;
  }
}

When I run docker-compose up -d and try to access the Laravel app through the htts://localhost:8000 I get this error on my screen

UnexpectedValueException
The stream or file "/var/www/html/storage/logs/laravel.log" could not be opened: failed to open stream: Permission denied

I have run sudo chown lykos:lykos -R ./src from my root-app-dir but the issue is still there. How can I fix this?

its not on wbserver, its on my local environment. I'm basically trying to set my repositories locally run on docker — ltdev, May 27 '18 at 14:18
i meant `nginx`, are you sure the process is running as your own user? or a nginx related user? — Quezler, May 27 '18 at 14:19
Let us [continue this discussion in chat](https://chat.stackoverflow.com/rooms/171869/discussion-between-quezler-and-lykos). — Quezler, May 27 '18 at 14:23

score 29 · Accepted Answer · edited Feb 25 '20 at 05:42

29

There are several options, what could be wrong:

The storage link isn't properly set, you can read about it here, after launching app container, you should do php artisan storage:link to check whether proper link is there
You don't have the proper right for the given folder, from default, logs folder should have www-data writable rights, you can check that by ssh to machine and the do ls -l on files in /var/www/html/[your laravel app], if not, add the proper rights by: chown -R www-data:www-data *
Also related to file permissions: you can disable SELinux (but only in dev server, never do it on live) by cehcking the status: sestatus and then enforcing it to 0 by setenforce 0 (however on live server, it's better to leave SElinux running and try to disable the problem by chcon -R -t httpd_sys_rw_content_t [path to storage folder here]

edited Feb 25 '20 at 05:42

Caleb

122,179
19
178
268

answered May 27 '18 at 14:22

Tooschee

531
4
8

I am having "chcon: can't apply partial context to unlabeled file" when I do chcon -R -t httpd_sys_rw_content_t – Utku Dalmaz Nov 02 '20 at 06:36
1

Note that the container would create `/var/www/html/storage/logs/laravel.log` by `root:root` hence you should run `chown -R www-data:www-data .` on root of the project. Next, the PHP would append logs to the mentioned file obviously by `www-data:www-data`. – M. Rostami Nov 08 '20 at 14:21
The third one saved me. thanks – M.Arjmandi May 14 '22 at 06:41

score 27 · Answer 2 · edited May 12 '21 at 21:22

27

if the above does not work when its added to your .env file the following will:

sudo chmod o+w ./storage/ -R

this will give others permissions without altering user and group permissions.

edited May 12 '21 at 21:22

Dharman

26,923
21
73
125

answered May 12 '21 at 21:16

Developer Jay

555
1
7
14

This is just a disingenuous way of using `chmod 777`. It's very dangerous, and allows **anyone** to alter the files served to end users. – miken32 Jan 10 '22 at 16:51

mischkez · Answer 3 · 2021-05-10T15:59:12.473

15

if you are using laravel sail, add following to your .env file

WWWGROUP=1000
WWWUSER=1000

edited May 10 '21 at 15:59

answered May 09 '21 at 12:09

mischkez

318
4
8

Rob Mascaro · Answer 4 · 2021-10-08T07:13:46.347

11

If you're using Sail on Docker Windows Desktop with WSL2 this issue arises when you start the docker container directly from the dashboard. Instead, start the container within your WSL2 terminal instance i.e

sail up -d

edited Oct 08 '21 at 07:13

answered Aug 24 '21 at 09:09

Rob Mascaro

617
5
15

Yup seems to be the case for me aswell. – Blaze Clone May 17 '22 at 19:16

score 0 · Answer 5 · answered Jul 27 '21 at 04:46

0

With user root:root . You try with command : sudo chmod -R 777 storage/
With user www-data:www-data . You try with command :
- sudo chown -R www-data:www-data storage/
- sudo chmod -R 755 storage/
If you use Docker . You try with command :
- sudo chown -R nginx:nginx storage/
- sudo chmod -R 755 storage/

answered Jul 27 '21 at 04:46

Nam Sama

45
3

pls, if it's true, like :3. – Nam Sama Aug 03 '21 at 09:12

score 0 · Answer 6 · edited Sep 11 '21 at 13:53

I had this issue because I was using sail and the default directory for the logs thinks I am using Apache. I could not find any way of changing the log location to the correct storage folder, so I created a symbolic link instead:

ln -s /var/www/html/public/storage /home/<yourfoldername>/storage

When I ran my script again, it errored properly, and wrote to laravel.log file in the correct location

Laravel & Docker: The stream or file "/var/www/html/storage/logs/laravel.log" could not be opened: failed to open stream: Permission denied

6 Answers6

Linked