docker-compose inspect

[pmihalcin]

Hi all,
Are there any plans for docker-compose inspect command?
One could get e.g. exposed ports of given service

Thanks

[shin-]

docker-compose ps already lets you see exposed ports.

[jsrun]

Hello friend, I made a module to solve this https://github.com/jsrun/docker-compose-remote-api

[ahilsend]

I agree! It would be very useful to have the commands available to docker itself also available to docker-compose.

[awalterschulze]

Why was this closed?

[shin-]

It won't be implemented. For the rare cases where it would be useful, people can use docker inspect instead.

[awalterschulze]

docker inspect only works if you setup your --project_name correctly.
But then I am also happy with docker inspect.

[elboletaire]

I don't get it... why is then docker-compose exec implemented? or docker-compose logs?

[RyanEwen]

+1

I would like to be able to write a script to check if a container is running but if the containers were started using compose and not named, then I don't know the name.

[dsaborg-waya]

It would be great to be able to inspect docker-compose containers so one does not need to know the project name beforehand.

[deeky666]

For what it's worth: You can do something like (assuming the service to check is named foo)

docker inspect $(docker-compose ps -q foo)

Hope that helps.

[mihow]

Is there a way to get the docker-compose project name programmatically? docker inspect isn't an option if a script can't determine the project name that compose generated.

For example, there is no consistent way to remove named volumes programmatically.

[larssb]

@deeky666

I tried your suggestion and it works well for docker-compose.yml service definitions where one did not use --project-name. However, if that is what one did, it does not work as docker-compose ps -q _servicename_ returns nothing.

Is there anything one can do in the case described above?

Thank you

[deeky666]

@larssb I'm not sure if I get you right but maybe this helps?

docker inspect $(docker-compose --project-name PROJECT_NAME ps -q SERVICE_NAME)

[larssb]

Hi @deeky666

Sure ... I might not have explained myself properly. If I for some reason, forgot, lost or for whatever reason, do not have the project name used. So I can't use the --project-name parameter to docker-compose ps ... is there then a way by which I can determine the project name that was used.

Thank you.

[rafipiccolo]

If I do
docker-compose --project-name project up -d service

I get a container named : project_service_1

Then this will return data
Docker inspect $(docker ps -aq | grep _service_ )

Ez but shame.

[thenewguy]

I just happened across this issue trying to debug an odd problem with a container where I need to inspect one of the compose containers from inside a CI script. It seems bizarre not to include an easy to use docker-compose inspect option

[quant61]

You can inspect docker-compose containers like this:

docker inspect $(docker ps -f label=com.docker.compose.project.working_dir="$PWD" -f label=com.docker.compose.service=service_name --format '{{.ID}}')

If you want to use container id in scripts, you can do this:

CONTAINER_ID=$(docker ps -f label=com.docker.compose.project.working_dir="$PWD" -f label=com.docker.compose.service=service_name --format '{{.ID}}')

[thenewguy]

You can inspect docker-compose containers like this:

docker inspect $(docker ps -f label=com.docker.compose.project.working_dir="$PWD" -f label=com.docker.compose.service=service_name --format '{{.ID}}')

If you want to use container id in scripts, you can do this:

CONTAINER_ID=$(docker ps -f label=com.docker.compose.project.working_dir="$PWD" -f label=com.docker.compose.service=service_name --format '{{.ID}}')

Thank you for putting that together. I will make use of it.

It is still rather obscure and complicated for interacting with the cli by hand. It isn't viewable without scrolling on a 3000px wide monitor =P

docker-compose inspect db would be much easier to use