Container images in Docker Hub are missing 'data/v2/csv'

[RamType0]

Container images in Docker Hub are missing 'data/v2/csv'.
So we could not build db.

[Naramsim]

Hi, this is the intended behavior. In the past we had data in it but the images were too heavy.

You should download this repository and mount the data/sprites inside the container.

You can use the supplied docker compose files

[RamType0]

Hi, this is the intended behavior. In the past we had data in it but the images were too heavy.

So what is the usage of container images in Docker Hub?

It seems like we always need to build image from cloned repository and container images in Docker Hub could not be used any time.

[RamType0]

IMHO, usable huge container image is far much better than unusable small container image.
Some of popular container images are huge.
Ollama (0.16.1) has size of 3.11GB.

[Naramsim]

Hi, to spin up PokeAPI's service you need the docker compose file, the Docker image alone isn't enough as of now. In the compose file there are some dependencies such as postgres, etc. Since you need the repo to run the compose file the data is already present, so there's no need to put it in the image as well. Moreover the image now is light and downloads fast.

It seems like we always need to build image from cloned repository and container images in Docker Hub could not be used any time.

This is not true, if you execute the command on the README (make docker-setup) the image is pulled from Docker Hub, Compose will mount a volume in the container sharing the repository data and build the DB.

What we could do is create another image, such as pokeapi/pokeapi:master-standalone that uses sqlite as db, and exposes data with the internal server.

Even better we could create an image that has the DB already loaded, without the need to build it locally! This is interesting, and the image would be ready to serve requests instantly.

Anyways, as of now stick to the instructions written on the README