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

Workflow store points to model store in docker container #2792

Closed
agunapal opened this issue Nov 14, 2023 · 0 comments
Closed

Workflow store points to model store in docker container #2792

agunapal opened this issue Nov 14, 2023 · 0 comments
Labels
bug Something isn't working internal Issues found internally

Comments

@agunapal
Copy link
Collaborator

agunapal commented Nov 14, 2023

🐛 Describe the bug

On loading the docker image, I see that the workflow store is pointing to model_store instead of wf_store

Error logs

docker run --rm -it -p 127.0.0.1:8080:8080 -p 127.0.0.1:8081:8081 -p 127.0.0.1:8082:8082 -v $(pwd)/wf_store:/home/model-server/wf-store -v $(pwd)/model_store:/home/model-server/model-store pytorch/torchserve:latest-cpu
Unable to find image 'pytorch/torchserve:latest-cpu' locally
latest-cpu: Pulling from pytorch/torchserve
edaedc954fb5: Pull complete 
c9d9b88802cc: Pull complete 
d5afda4d2e5c: Pull complete 
ce8cdd9a8987: Pull complete 
8cd86b878314: Pull complete 
d3fa9c22238a: Pull complete 
086f768fc1c4: Pull complete 
aea4c999a5d1: Pull complete 
4f4fb700ef54: Pull complete 
Digest: sha256:eac4deea2e237db904d67175a7b3e075d4e110a83b23a249679093ea32017d2d
Status: Downloaded newer image for pytorch/torchserve:latest-cpu
WARNING: sun.reflect.Reflection.getCallerClass is not supported. This will impact performance.
2023-11-14T19:04:42,884 [WARN ] main org.pytorch.serve.util.ConfigManager - Your torchserve instance can access any URL to load models. When deploying to production, make sure to limit the set of allowed_urls in config.properties
2023-11-14T19:04:42,886 [INFO ] main org.pytorch.serve.servingsdk.impl.PluginsManager - Initializing plugins manager...
2023-11-14T19:04:42,947 [INFO ] main org.pytorch.serve.metrics.configuration.MetricConfiguration - Successfully loaded metrics configuration from /home/venv/lib/python3.9/site-packages/ts/configs/metrics.yaml
2023-11-14T19:04:43,047 [INFO ] main org.pytorch.serve.ModelServer - 
Torchserve version: 0.9.0
TS Home: /home/venv/lib/python3.9/site-packages
Current directory: /home/model-server
Temp directory: /home/model-server/tmp
Metrics config path: /home/venv/lib/python3.9/site-packages/ts/configs/metrics.yaml
Number of GPUs: 0
Number of CPUs: 8
Max heap size: 7936 M
Python executable: /home/venv/bin/python
Config file: /home/model-server/config.properties
Inference address: http://0.0.0.0:8080
Management address: http://0.0.0.0:8081
Metrics address: http://0.0.0.0:8082
Model Store: /home/model-server/model-store
Initial Models: N/A
Log dir: /home/model-server/logs
Metrics dir: /home/model-server/logs
Netty threads: 32
Netty client threads: 0
Default workers per model: 8
Blacklist Regex: N/A
Maximum Response Size: 6553500
Maximum Request Size: 6553500
Limit Maximum Image Pixels: true
Prefer direct buffer: false
Allowed Urls: [file://.*|http(s)?://.*]
Custom python dependency for model allowed: false
Enable metrics API: true
Metrics mode: log
Disable system metrics: false
**Workflow Store: /home/model-server/model-store**

Installation instructions

Docker 0.9.0

Model Packaing

NA

config.properties

No response

Versions

0.9.0

Repro instructions

Command in logs above

Possible Solution

Place the .war file in model_store

@agunapal agunapal added bug Something isn't working internal Issues found internally labels Nov 14, 2023
@udaij12 udaij12 closed this as completed Nov 20, 2023
github-merge-queue bot pushed a commit that referenced this issue Nov 20, 2023
* fixed workflow store pathing

* fixed lint

* doc change and added test

* fixed test

* added new test

* fixed properties file
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working internal Issues found internally
Projects
None yet
Development

No branches or pull requests

2 participants