CosmiQ / solaris

CosmiQ Works Geospatial Machine Learning Analysis Toolkit
https://solaris.readthedocs.io
Apache License 2.0
413 stars 112 forks source link

[BUG]: docker ports are not exposed after building the supplied CPU dockerfile. #411

Closed AH-Merii closed 3 years ago

AH-Merii commented 3 years ago

Thank you for helping us improve solaris!

Summary of the bug

I am attempting to run the dockerfile found in the repo. When I run docker ps -a after building and running the image, the ports end up not being exposed.

Steps to reproduce the bug

After building the image I proceed to running it by evoking the command below:

docker run -p localhost:8888:8888 -p localhost:6006:6006 1ff 

Steps to reproduce the behavior:

  1. Build the image using: docker build .
  2. Run the image using: docker run -p localhost:8888:8888 -p localhost:6006:6006 1ff
  3. Check whether the ports are exposed by running docker ps -a
  4. I end up getting the below image, where you can clearly see that the ports are not exposed.

Buggy behavior and/or error message

The ports are not exposed as expected.

Expected behavior

The ports should be exposed on ports 8888 and 6006.

Screenshots

dockerps

Environment information

Additional context

I am using the dockerfile for CPU.

AH-Merii commented 3 years ago

I needed to run the container in an interactive terminal using the -it flag or in detached mode, the problem was that the container was exiting immediately.