Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.

dmanagement@lrg.co.uk's avatar

forced to restart docker on every file change

I have experienced a weird issue using laravel and laradock

Whenever i made a change to any file, even if it was just a string change in a template the page would fail to load next time i refreshed the browser. and the workspace container would fail to stop when i ran docker-compose down.

i had to restart docker, then run docker compose down and then restart my containers for any changes to the project to take effect.

i created a new laravel project with its own instance of laradock and it was fine. until i copy/pasted my files from the project which had the error at which point the problem started again.

cache clears, view clears, compose dump-autoload and deleting + reinstalling the composer dependancies did not fix the issue.

The only file changes i had made (which i also copied to the second project) was a laravel template, a laravel layout template, a component template and a component controller.

I have replicated this issue in a new project

It only seams to happen if i modify a blade template file and the only thing which appears in the logs which looks wrong is this

1:50:27.955552049Z" level=warning msg="Running modprobe bridge br_netfilter failed with message: ip: can't find device 'bridge'\nip: can't find device 'br_netfilter'\nmodprobe: can't change directory to '/lib/modules': No such file or directory\n, error: exit status 1"

any idea what is going on

0 likes
1 reply

Please or to participate in this conversation.