We made an effort to load the dependencies to automate the training. For composer, it didn't load a vendor directory. When running npm install, it didnt load a node_modules directory.
This forced us to run those commands twice after docker-compose loaded the containers.
One observation: there might be a perms issue. After running the follow up command, things were owned by root on the host filesystem (not the user running the docker-compose command).
We made an effort to load the dependencies to automate the training. For composer, it didn't load a vendor directory. When running npm install, it didnt load a node_modules directory.
This forced us to run those commands twice after docker-compose loaded the containers.
One observation: there might be a perms issue. After running the follow up command, things were owned by root on the host filesystem (not the user running the docker-compose command).