Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: The ports on which the serving function runs and the container redirection do not match #4441

Open
2 tasks done
Nikitala0014 opened this issue Oct 7, 2023 · 2 comments

Comments

@Nikitala0014
Copy link

MLRun Version checks

  • I have checked that this issue has not already been reported.

  • I have confirmed this bug exists on the latest version of MLRun CE.

Reproducible Example

serving_fn.invoke(path=model_inference_path, body={"inputs": [sample_id]})

Issue Description

After deployment this function returns the following error: Max retries exceeded. I use a stable address. Therefore, there is a connection to the container.
The problem is that container port to 8080 inside: c3422c55e73d nuclio/processor-stock-prediction-chris-stocks-serving:latest "processor" 20 seconds ago Up 19 seconds (healthy) 0.0.0.0:32810->8080/tcp, :::32810->8080/tcp nuclio-nuclio-stock-prediction-chris-stocks-serving
But the service inside container working on 8082

Expected Behavior

Failed to establish a new connection: [Errno 111] Connection refused

Installation OS

Linux

Installation Method

Docker

Python Version

3.9

MLRun Version

1.4.0

Additional Information

No response

@Nikitala0014
Copy link
Author

image
Inside the container

@Nikitala0014
Copy link
Author

image
As far as I understand from the code, all the logic happens in the mlrun container, and the code simply calls the build method "build/function" with this arguments.
This means that nothing I can do from the project code to resolve this. The problem is in some initial configuration

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant