client.containers API documentation seems outdated

[jelovac]

Hi,

Documentation (both docs and readme.md) state that we can manage containers using client.containers API.

However when I use the following piece of code obtained from README.md:

import docker

client = docker.from_env()

container = client.containers.get('45e6d2de7c54')

I am getting the following error:

AttributeError: 'function' object has no attribute 'get'

I am getting the same thing for client.containers.list().

It seems that method signature changed.

Digging through the code I figured out that I should be able to get the container info like this:

container = client.containers(filters={"id": "45e6d2de7c54"})

However this does not return Container object on which I could do certain actions and instead returns plain dictionary with the result set which I assume is the one from Docker API.

Am I doing something wrong? Can I still get the actual container object like it is documented in the docs?

I am using version 6.0.1 installed through pip. My python version is 3.10.6

[naufalafif]

Not sure, but it's working from my side.
I am using same setup. docker-py 6.0.1 and python 3.10.6

the code is there, there's no changes on the API

docker-py/docker/models/containers.py

Lines 919 to 936 in aaf68b7

	def get(self, container_id):
	"""
	Get a container by name or ID.
	Args:
	container_id (str): Container name or ID.
	Returns:
	A :py:class:`Container` object.
	Raises:
	:py:class:`docker.errors.NotFound`
	If the container does not exist.
	:py:class:`docker.errors.APIError`
	If the server returns an error.
	"""
	resp = self.client.api.inspect_container(container_id)
	return self.prepare_model(resp)

[whydinkov]

Edit:

Maybe you have installed docker-py instead of docker?

---

Original comment:
Check the version of docker-py.

I am using poetry and just by writing poetry add --group dev docker-py it installed

docker-py = "^1.10.6"

which given the current main version (6) seems quite outdated, however I had the same problems in code, mentioned by you @jelovac and it was very weird for me, why documentation seemed so outdated.