@habibalsa subjected package [irrespective whether it is installed by user or preinstalled] can be upgraded through pip. At times the upgrade/install of packages may fail due to need root access or overlap with kernel libraries file, in those case it is recommended to have a custom image with required packages/version combinations built.  https://docs.cloudera.com/machine-learning/cloud/runtimes/topics/ml-creating-a-customized-runtimes-image.html ... View more

Hi Dankenstein, Thanks for your post. Considering the nature of the query, may I request you to create a support case. Besides, I would encourage you review the Cloudera Machine Learning which will be replacing the CDSW after its End of Support [May 2024]. https://docs.cloudera.com/machine-learning/1.5.0/private-cloud-requirements/topics/ml-getting-started.html https://docs.cloudera.com/machine-learning/cloud/index.html https://www.cloudera.com/legal/policies/support-lifecycle-policy.html ... View more

CDSW/CML uses brackets editor. You may have a look at the brackets documentations for further customisation needs. ... View more

seems to be a gap in the exception handling.  Could you please share the actual script snippet for analysis. ... View more

Below snip indicate auth failure with the Cloudera paywall. Can you try "docker login" with your paywall credentials. Presume that could mitigate the 401 response.  E: Failed to fetch https://archive.cloudera.com/cdh6/6.2.0/ubuntu1804/apt/dists/bionic-cdh6/InRelease 401 Authentication required [IP: 199.232.8.167 443] E: The repository 'https://archive.cloudera.com/cdh6/6.2.0/ubuntu1804/apt bionic-cdh6 InRelease' is no longer signed. ... View more

Preinstalled packages can be upgraded based on the business requirement.  I am curios to know what is the runtime version being used? By any chance did you test in the latest available runtime version? ... View more

  Visuals right side menu > build > Under field properties, display format   hope this helps. ... View more

@lafi_oussama    Was the kubectl command executed as root?   If not, could you please try as root and share the output? If yes, the response indicates that the Kube API server is not up. pls share the output of ps -ef | grep -i kube from master node.   By the way, how many nodes in CDSW.   ... View more

@lafi_oussama     From the error message on the weave reset, seems the docker daemon is not running or it's unable to handshake with the underlying network.   Since CDSW 1.6 stale configurations will be removed during the restart itself.  Could you please try to review the application by these steps.   > stop all roles in CDSW > validate no services with kubernetes running in the node [ps -ef | grep -i kube]. if so kill them > start the master node alone -- if the service has more than one node 1) docker daemon [DD] 2) master  3) application > wait for a while as such the pods get created [ this may take 10 - 15 mins] > once the application comes up, then start adding the worker node one after the other by starting roles in this order 1) DD 2) worker   if the service runs on a single node and the role by role start does not work, share the output of below command from the master node. `kubectl get pods --all-namespaces` ... View more