I don’t know the image, but it is completely possible that there are no logs because it failes before it could write anything. In order to find out what it was caused by, you should find out what the error code means in case of the software that is running in the container. The maintainer of the image could probably tell you what the error code means. I also found the community forum of qiime2
They can probably help you more, but I can share some general ideas:
- Sometimes the host operating system is not compatible with the container. It is rare, but it can happen.
- It could be that the parameters, configurations have changed and your old parameters make the container fail created from the new image.
- Sometimes the Docker version is too old and some system calls can’t doesn’t work through Docker.
- Sometimes the logs are not properly sent to the standard output and error stream so you don’t see it with
docker logsbut you can browse the content of a stopped container or copy the content out to investigate.
I talked about some ideas on a Docker Community All-Hands event and there is also a blogpost about it where you can find my video too: