[SUGGESTION] Remove /var/ folder from composer installation in docker volume

[Wingmk]

Currently the TYPO3 backend is slow in docker installations. Even if a delegated volume is mounted.
If TYPO3 is setup as composer we can stop mounting the /var/ folder to the docker container.

I ran some Tests after removing the folder from mounting to docker and it runs a lot faster, especially the backend.

There might also be reasons to remove the typo3temp folder from mounting inside the docker container, but currently I don't even know what or why TYPO3 stores still data inside that directory.

[mediaessenz]

Can you explain, how do you did this exclusion?

[Wingmk]

@mediaessenz I changed the volumes inside the docker-compose.yaml from

volumes:
  - ./app/:/app/:delegated

to

volumes:
  - ./app/config:/app/config
  - ./app/vendor:/app/vendor
  - ./app/web:/app/web

This way the app folder itself and therefore the /var/ folder does sync itself with the docker system.
This does also means that the root of the project is not complete. e.g. /var/, composer.json, composer.lock

[mediaessenz]

Thank you for the explaination.

To bad that there is no easier way to exclude some files or subfolder, like it is possible in eg. .gitignore files

[htuscher]

You can do this:

version: '3.7'
services:
  app:
    volumes:
      - ./app:/app:cached
      - app-cache:/app/var:nocopy
volumes:
  app-cache:

[Wingmk]

@hhoechtl Does this setup work for you?
It looks like the /app/var directory inside the container is not writable by the TYPO3 application.
Having the folder empty on the clientside and filled by the application inside the docker container is the desired outcome.

[htuscher]

Yes that works, but you have to do chown 1000:1000 /app/var inside of the container once of course.

[Wingmk]

@hhoechtl can you put this inside a Dockerfile so this is executed on container creation?
A manual chown would not be a great solution.

[htuscher]

Of course you could. I'm personally not supporting TYPO3 anymore. Am Do., 26. März 2020 um 08:46 Uhr schrieb TimoWinkler < notifications@github.com>:

…

@hhoechtl <https://github.com/hhoechtl> can you put this inside a Dockerfile so this is executed on container creation? A manual chown would not be a great solution. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#202 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABGXLBG6DVS65NAOJT7W4UTRJMB4DANCNFSM4JNMZBAQ> .

-- *Onedrop GmbH & Co. KG* Dr.-Leo-Ritter-Str. 2 93049 Regensburg Tel. +49 (0) 941 / 206 064 - 40 1drop.de hhoechtl@1drop.de <rzierhofer@1drop.de> http://www.facebook.com/onedropsolutions http://twitter.com/1drop

[Wingmk]

@hhoechtl I did some reading and I don't think this stops synchronising the /var folder.
It instead pushes the volume location for synchronising the var folder to docker.

[htuscher]

Not it won't stop the synchronisation, but as you don't make changes locally in the var folder and it's overlayed inside the container with the nocopy volume, it doesn't matter. The nocopy volume is docker engine internally and therefore fast.

[mediaessenz]

@hhoechtl
I have added this to my Dockerfile.development, right after WORKDIR /app/:

RUN mkdir /app/var && chown 1000:1000 /app/var

Additional I added your suggestion to my docker-compose.yml:

version: '3.7'
services:
  app:
    volumes:
      - ./app:/app:cached
      - app-cache:/app/var:nocopy
volumes:
  app-cache:

After all I rebuild the app container and started all again and get this error when opening the app in the browser:

Fatal error: Uncaught RuntimeException: Could not create directory "/app/var/log/"! in /app/public/typo3/sysext/core/Classes/Utility/GeneralUtility.php on line 2169

Did I forget/missunderstand something?

[htuscher]

Creating the directory upfront doesn't work.
The volume mount will override that and still belongs to root

[mediaessenz]

But how can I change the owner/group later?

[htuscher]

docker exec {container} chown 1000:1000 /app/var

[mediaessenz]

Is there also a way to do this automaticaly after "docker-compose up" with the right container name?