Review the containers' output in your terminal. If it was run in detached mode (with
-d flag) then the you can review its output using
docker container logs <container name>.
If the container doesn't behave as planned but also doesn't exit, you may want to diagnose parts of your application from inside the container. You can do this by creating an interactive shell inside it with the command:
docker container exec -it <container name> sh.
Another way to interact with the container's file system would be to mount some of its content on the host machine, then you will have it available to any tools you might want to use from your machine. This can be done by adding the option
-v /path/on/host:/path/in/container when running the image.
For a more focused answer, it will help if you provide an example of what Error or behavior occurs.