Wrong permissions since latest (29.09.2018) master branch

[paifgx]

ISSUE TYPE

• Question

SUMMARY

I get following error in the devilbox backend:

Warning: session_start(): open(/tmp/sess_c791ba8151497dec229b136e06bf3b22, O_RDWR) failed: Permission denied (13) in /var/www/default/config.php on line 6

Warning: session_start(): Failed to read session data: files (path: ) in /var/www/default/config.php on line 6

if i want to connect via phpmyadmin i get:

Error during session start; please check your PHP and/or webserver log file and configure your PHP installation properly. Also ensure that cookies are enabled in your browser.

session_start(): open(SESSION_FILE, O_RDWR) failed: Permission denied (13)

session_start(): Failed to read session data: files (path: )

in the console i get:

php_1    | [29-Sep-2018 19:53:20 Europe/Berlin] mail() on [/var/www/default/include/lib/Logger.php:142]: To: apache@localhost -- Headers:  -- Subject: devilbox error
php_1    | Sep 29 19:53:20 php postfix/postdrop[3313]: warning: mail_queue_enter: create file maildrop/577422.3313: Permission denied
php_1    | Sep 29 19:53:30 php postfix/postdrop[2591]: warning: mail_queue_enter: create file maildrop/425317.2591: Permission denied
php_1    | Sep 29 19:53:30 php postfix/postdrop[3313]: warning: mail_queue_enter: create file maildrop/577629.3313: Permission denied
php_1    | Sep 29 19:53:40 php postfix/postdrop[2591]: warning: mail_queue_enter: create file maildrop/425513.2591: Permission denied
php_1    | Sep 29 19:53:40 php postfix/postdrop[3313]: warning: mail_queue_enter: create file maildrop/577860.3313: Permission denied

what i do wrong? i doesn't change anything. i only pull the latest master branch and then it crashes.. (OS: Ubuntu 18)

Goal

get the tool running again :-(

[cytopia]

@paifgx thanks for submitting this issue. This rather looks like a bug to me and I would require a lot more information in order to reproduce. Can you convert (or add) all the required fields from the bug report template: https://github.com/cytopia/devilbox/issues/new?template=bug_report.md

[paifgx]

Checklist

• .env file is attached
  env.txt
• docker-compose.override.yml is attached (if it exists)
• Custom configs from cfg/ dir are attached (if customized)
  apcu.txt
  devilbox.txt
• docker-compose logs and log/ output is added
• I've looked through the docs: https://devilbox.readthedocs.io/en/latest/
• I've looked through existing issues: https://github.com/cytopia/devilbox/issues

OS / ENVIRONMENT

1. Host operating system and version: Ubuntu 18.04.1 LTS
2. (Windows) Native Docker or Docker Toolbox: native
3. Docker version: Docker version 18.06.1-ce, build e68fc7a
4. Docker Compose version: Docker version 18.06.1-ce, build e68fc7a
5. (Linux) Is SELinux enabled?: no
6. What git commit hash are you on?: -

OTHER INFORMATION

Start command

$ docker-compose up
$ docker-compose up php httpd bind mysql

File and user permissions (Linux & MacOS)

$ id

1000

$ ls -la

$ ls -la data/www

[cytopia]

The directory permissions look fine from what I can see.

I've applied your .env and also added apcu.ini and devilbox.ini to cfg/php-ini-7.2/

I logged into phpMyAdmin and it just worked fine.

What urls are you calling exactly and where does this error appear (website, logfile, etc) and can you also paste the full docker-compose logs output

[cytopia]

Additionally there seems to be an issue with Docker 18.06.1-ce, also reported by others here: #374

I would suggest to downgrade Docker back to 18.06.0-ce and see if that works

[cytopia]

@paifgx can you switch to the release branch for v1.0.0. The PR and the description is here: #416

Let me know if this fixes your issue.

[dvlbot]

Stale issue

This issue was marked with waiting for reply and did not receive an answer for a long time. If the requested information is not provided, it will be auto-closed.

Beep beep, I am a bot - do not reply to me.

[paifgx]

all seems to working fine now. thanks & sorry for long response.

[cytopia]

OK, glad to hear. Just stick to the above named branch (until it will finally be merged to master). I will constantly rebase it with latest changes from master, so ensure to read the comment in the PR for how to properly update this branch.