styles.css not updating when running in docker

I have a tailwind service in my docker-compose.yml with the following command: command: "python manage.py tailwind start"

For some reason, it does not update the styles.css But if I exec into the same container and then manually run the same command, it does update the file

Here are the logs of the command running using docker-compose:

> theme@2.2.1 dev:sync

> run-p dev:tailwind sync



> theme@2.2.1 sync

> browser-sync start --config bs.config.js



> theme@2.2.1 dev:tailwind

> cross-env NODE_ENV=development tailwindcss --postcss -i ./src/styles.css -o ../static/css/dist/styles.css -w


[Browsersync] Watching files...

And here are the logs when I use exec to run the same command on the same container:

> theme@2.2.1 dev:sync
> run-p dev:tailwind sync


> theme@2.2.1 dev:tailwind
> cross-env NODE_ENV=development tailwindcss --postcss -i ./src/styles.css -o ../static/css/dist/styles.css -w


> theme@2.2.1 sync
> browser-sync start --config bs.config.js

[Browsersync] Watching files...

warn - You have enabled the JIT engine which is currently in preview.
warn - Preview features are not covered by semver, may introduce breaking changes, and can change at any time.

Rebuilding...
Done in 307ms.
[Browsersync] File event [change] : ../static/css/dist/styles.css

[trey]

Yes, there is.

Thank you, @roushikk! I’m still a Docker noob in many ways. Thanks for showing me a better way! 😃

[roushikk]

Is there a standard way of then not running that service in production?

Yes, there is. You usually have a base docker-compose.yml file and you extend it for different environments like dev, staging and production.

So, you’ll have a base docker-compose.yml file without the tailwind service and then you’ll have a docker-compose.dev.yml in which you’ll add the tailwind service.

Official Docker documentation: https://docs.docker.com/compose/extends/