Compose: docker-compose dry run

[ghost]

Would like insight to what docker-compose generates/executes

[aanand]

Agreed - for the time being, you can use docker-compose --verbose to see what it's doing.

[paurullan]

This would be incredibly useful for debugging purposes.

[jmkgreen]

So config just said my file was fine yet up told me a service was linked to a service not described.

Does config need to be improved or is dry-run intended for this? Gut tells me the former...

[dnephin]

config should catch these errors, we don't currently for links (however we do for depends_on).

I created #2933

[ekristen]

+1 this would be a great feature

[atrauzzi]

Something like this would be extremely helpful in debugging situations like https://github.com/docker/compose/issues/3259.

Currently --verbose isn't showing me any information about volumes/bind-mounts.

[hervenicol]

I am also looking for a dry-run feature, that would not change anything but would explain whether it would perform any action in a normal run.

[xandreklein]

+1

[decentral1se]

+1

[jars]

+1

If docker-compose <cmd> builds a lengthy docker command and executes it, (like in up and build) that generated command should be discoverable with some flag for debugging... perhaps --dry-run.

[yaanst]

+1

[dsaydon90]

+1

[mooperd]

+1

[emersonf]

Any news on this? It's been 3 years. At a minimum knowing which services are going to be restarted would allow automated notifications of downtime.

[zethis]

+1

[l0k3ndr]

+1

[dugajean]

This would be great to have.

[gniewomir]

+1

[ivanleoncz]

+1

[ehrlichja]

+1

[whi-tw]

+1

[afonsosantos]

+1 for AzuraCast @ https://azuracast.com and https://github.com/AzuraCast/AzuraCast

[anhtuan84]

+1

[DanielBryars]

+1 --dry-run would enable diagnostics, and also provide a way to validate it's going to do what you expect before a production change.

[hinorashi]

I'm still here waiting for this dry run feature :D

[pravynandas]

+1 in 2020.

[wfehrnstrom]

+1

[biscaldis]

+1

[lweberru]

+1

[pablog12]

+1

[pallsopp]

+1
5 years later :)

[cntsw]

+1

[Victor-D]

Hello

For monitoring purpose I am looking for a command to check if images in a docker-compose file are all up-to-date.

A docker-compose pull --dry-run would do the trick.

[ilyaevseev]

+1
It seems to be "must have" feature.

[lweberru]

+1
For a 5 years old feature request :(

[ForestJohnson]

I am using

docker-compose config --hash="servicename"

combined with

docker inspect <containername> -f '{{index .Config.Labels "com.docker.compose.config-hash"}}'

to roll my own docker-compose --plan up / docker-compose --dry-run up per this users idea: https://stackoverflow.com/questions/47287745/how-to-check-if-container-is-up-to-date#answer-56165526