You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
18-09-18:10:13:51 INFO [docker_container_manager.py:257] Found 0 replicas for sum-model:1. Adding 1
I print the docker's healthy status (unhealthy)
18-09-18:10:13:52 INFO [docker_container_manager.py:272] Container status: running, Docker healthy status: starting
18-09-18:10:13:55 INFO [docker_container_manager.py:272] Container status: running, Docker healthy status: unhealthy
The container log shows that
Starting Python Closure container
Connecting to Clipper with default port: 7000
Traceback (most recent call last):
File "/container/python_closure_container.py", line 56, in
rpc_service.get_input_type())
File "/container/python_closure_container.py", line 28, in init
self.predict_func = load_predict_func(predict_path)
File "/container/python_closure_container.py", line 17, in load_predict_func
return cloudpickle.load(serialized_func_file)
File "/usr/local/lib/python3.5/site-packages/cloudpickle/cloudpickle.py", line 1044, in _make_skel_func
base_globals['builtins'] = builtins
TypeError: 'str' object does not support item assignment
Encountered error not related to missing packages. Please refer to the container log to diagnose.
Any help would be really appreciated!
The text was updated successfully, but these errors were encountered:
@FrankY-Sa :
I think that the latest release(v0.5.6) of cloudpickle causes this problem. (link) Please downgrade it from v0.5.6 to v0.5.3 by applying this patch.
@withsmilo Thanks! others encountered the issue. The reason is that my local cloudpickle version(0.5.5) is higher than the one used in docker container(0.5.2), making them incompatible.
python3.5 clipper-develop quick_start: sum-model
Hi,
I tried deploying sum-model gets stuck on
I print the docker's healthy status (unhealthy)
The container log shows that
Any help would be really appreciated!
The text was updated successfully, but these errors were encountered: