The following bind contains a source url that does not exist:
type: bind
source: ./kepler/common/var/lib/kepler/data
target: /var/lib/kepler/data
If users were to run this normally an error would be encountered.
What did you expect to happen?
A kepler/common directory should already exist with the same data directory as in kepler
How can we reproduce it (as minimally and precisely as possible)?
Run docker compose up in the manifests/compose/dev directory
Anything else we need to know?
The format of the local models used in kepler seems completely different than the trained models produced by the model server. Thus, I think it would be better if this bind is removed now that models can be transferred locally with filepath in the Model Config.
Kepler image tag
latest
Deployment
[X] Model server
[ ] Estimator
[ ] Online trainer
[ ] Offline trainer
[ ] Profiler
Kepler model server image tag if deployed
Kepler estimator image tag if deployed
Kepler online trainer image tag if deployed
Kepler offline trainer image tag if deployed
Kepler profiler image tag if deployed
Kubernetes version
```console
$ kubectl version
# paste output here
```
Install tools
Kepler deployment config
For on kubernetes:
```console
$ KEPLER_NAMESPACE=kepler
# provide kepler configmap
$ kubectl get configmap kepler-cfm -n ${KEPLER_NAMESPACE}
# paste output here
# provide kepler model server configmap if Kepler Model Server is deployed
$ kubectl get configmap kepler-model-server-cfm -n ${KEPLER_NAMESPACE}
# paste output here
# provide kepler deployment description
$ kubectl describe deployment kepler-exporter -n ${KEPLER_NAMESPACE}
```
For standalone:
# put your Kepler command argument here
KaiyiLiu1234
commented
2 hours ago
What happened?
The following bind contains a source url that does not exist:
What did you expect to happen?
A kepler/common directory should already exist with the same data directory as in kepler
How can we reproduce it (as minimally and precisely as possible)?
Run docker compose up in the manifests/compose/dev directory
Anything else we need to know?
The format of the local models used in kepler seems completely different than the trained models produced by the model server. Thus, I think it would be better if this bind is removed now that models can be transferred locally with filepath in the Model Config.
Kepler image tag
Deployment
Kepler model server image tag if deployed
Kepler estimator image tag if deployed
Kepler online trainer image tag if deployed
Kepler offline trainer image tag if deployed
Kepler profiler image tag if deployed
Kubernetes version
Install tools
Kepler deployment config