Static view files not deployed on demand in developer mode

[arutr]

Description
After upgrading the Magento version inside the Docker container from 2.4.5 to 2.4.7, static view files have stopped being automatically deployed when developer mode is enabled. On the frontend I am getting 404 errors for static content.

After I run setup:upgrade and navigate to the storefront, in the pub/static folder inside the Docker container, there is only a frontend directory with a requirejs-config.js file - nothing else.

If I deploy static content manually using bin/magento setup:static-content:deploy, then everything is fine. Switching the application mode from developer to production and then back to developer doesn't fix the problem.

This issue goes away when I delete the app volume and recreate it. I guess this has something to do with the Docker volume itself.

I am using version 44.0.0 of docker-magento, running everything on macOS 26.1 and OrbStack 2.0.5.

Steps To Reproduce

1. This issue only occurs once in a while, thus I don't have a clear way of reproducing it. Last time this happened was after I upgraded the Magento version inside the Docker environment.

[dosubot]

Hi @arutr! I'm Dosu and I’m helping the docker-magento team.

This issue is likely related to how Docker volumes and static content are handled in the docker-magento setup, especially after an upgrade. The main appdata volume, which holds your Magento code and static files, can retain stale or incomplete static content after an upgrade, leading to 404s until the volume is reset or static content is redeployed. Nothing in the docker-magento scripts automatically clears or redeploys static files on upgrade, so old files can linger unless you manually clean them up or reset the volume. This explains why deleting and recreating the app volume resolves the problem, and why manual static content deployment also works.

On macOS with OrbStack, volume syncing issues can also occur, especially if file access permissions for OrbStack are not enabled in System Settings. Make sure OrbStack has the necessary permissions to access your files, as missing permissions can cause file access errors and prevent static files from being generated or served correctly (source).

For best results after upgrading Magento, either manually clear the pub/static directory (except .htaccess), reset the appdata volume, or run a full static content deploy. This will ensure that stale files do not interfere with on-demand static file generation in developer mode (source).

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}