Closed andrewvmail closed 2 years ago
This is expected behavior because docker-compose
does not track changes in a dockerfile.
Can you try it with docker-compose build
or docker-compose up --build
and see if the issue persists?
It does work with docker-compose up --build
i have to use docker-compose up -d --build
in my use case since I need it to run as a daemon not in foreground.
Closing thanks alot!
Awesome, glad it worked out!
I am using this github action with
docker-compose -d up
. Cache works but the cache doesn't seem to invalidate when I make changes to Dockerfiles that makes up the docker-compose.