https://outerbounds.com/ logo
Join Slack
Powered by
Hello, after using the image `netflixoss/metaflow_...
# ask-metaflow
a
Hello, after using the image 
netflixoss/metaflow_metadata_service:v2.4.13
and cloning the repo and building myself, both with build 
ARG UI_ENABLED="1"
and through the ENV, I do not understand why isnt the container listening on port 8083. According to README it is available and listening on 8083, and it was available in the version 2.4.3. This is 
ps aux
output from container:
Copy code
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name    
tcp        0      0 0.0.0.0:8080            0.0.0.0:*               LISTEN      21/python           
tcp        0      0 0.0.0.0:8082            0.0.0.0:*               LISTEN      11/python3          
tcp6       0      0 :::3000                 :::*                    LISTEN      -
✅ 1
I have also tried with UI_ENABLED=0, same result
I started it manually with: 
/opt/latest/bin/python3 -m services.ui_backend_service.ui_server
but I get 404 on main page?
Using root Dockerfile results in this, I had to use Dockerfile.ui_service
t
sorry for taking a while to get back to this. The comment in the readme about the UI being available is for the docker-compose meant for development only. If you are using the release image to launch services, you need to also specify a separate command when launching the image, as the default is for the metadata-service only. You seem to already have tried this out though so this shouldn't be an issue. Let me try out the published image to see if I can reproduce the issue
testing locally with the production image and this seems to work fine. What kind of 404 are you encountering? Example command (I'm running a dev db container locally separately):
Copy code
docker run -p 80:8083 -e MF_METADATA_DB_HOST=host.docker.internal netflixoss/metaflow_metadata_service:v2.4.13 "/opt/latest/bin/python3" "-m" "services.ui_backend_service.ui_server"
The UI is accessible just fine on localhost with this.
if I include 
UI_ENABLED=0
to the env, then as expected I get a 404, as the service is not serving the UI assets at that point anymore.
a
This was solved, thanks!
3 Views
Open in Slack
PreviousNext
Powered by