Doesn't work with docker-compose

[justin-pierce]

import time
from tqdm import tqdm

for i in tqdm(range(50), desc='debug'):
    time.sleep(0.1)

Then in terminal I see nothing until the loop has finished, and it just prints:

debug: 100% 50/50 [00:05<00:00, 9.81it/s]

My docker compose file has tty: true and os.isatty(sys.stdout.fileno()) returns true

[casperdcl]

Interesting. We provide a docker image
which seems to work fine for its intended use in CLI pipe mode.

What version of python are you using?

[justin-pierce]

Image: FROM python:3.6

Which is running 3.6.6

Have tried it on two different computers and in both MacOS Terminal and VS Code Terminal.

[sepbot]

The problem is not with Docker itself, but Docker Compose.

To reproduce the problem, you need to first write a docker-compose.yaml file for your Docker service. Then bring up everything up by running docker-compose up -d and then following the logs by running docker-compose logs -f (or just run without -d, it will run in foreground I believe). If you follow these steps, you will find that the tqdm log line will not get outputted until a newline has been fed to stdout of that particular container after the loop has finished.

The problem is not present if you just use Docker itself with the --tty flag.

[casperdcl]

thanks @sepbot - is this something that's been reported on the docker-compose repo?

[aneeshvartakavi]

I'm running into the same issue, are there any known workarounds or fixes for getting tqdm to work in docker compose?

[shahidammer]

Did anyone manage to get the progress bar in the docker-compose. Any workaround?

[sepbot]

Use docker-compose run instead of docker-compose up and tty: true in your service config

[waydegg]

Use docker-compose run instead of docker-compose up and tty: true in your service config

Just using docker-compose run in my compose yml worked for me (tty: true made no noticeable difference).

[sepbot]

Use docker-compose run instead of docker-compose up and tty: true in your service config

Just using docker-compose run in my compose yml worked for me (tty: true made no noticeable difference).

You're right, docker-compose run allocates a TTY by default. Didn't know that at the time.

[Ghost---Shadow]

This workaround works fine too. For those who want to keep using docker compose up

it = tqdm(total=len(arr))
for e in arr:
  it.update(1)
  print(it)

[YuchiSu-Rin]

This command can help if you are running in detach mode:

docker compose up -d
docker attach --sig-proxy=false [container-name]

https://docs.docker.com/reference/cli/docker/container/attach/

You must set tty: true to the service.