Hello, I am not sure I understand what you are trying to do. Those ports are already established when a Cloudera AI session starts up, you can see this by starting a session, then in the code editor, type: !env | grep -i port You can then use these in your code, like in the example here: https://docs.cloudera.com/machine-learning/1.5.4/projects/topics/ml-projects-embedded-web-applications-example-flask-application.html ... View more

Dear Mike, Thank you for your support. I would like to highlight that I do not have internet access within CDSW, as our Cloudera environment is fully air-gapped. From your previous message, I understand that you are suggesting I create a custom Docker image and run it accordingly. I have already created a custom Docker image — however, I would appreciate it if you could review it and provide your feedback. Additionally, could you clarify your expectations regarding the base operating system for the container image? and the Base image? For your reference, we are using CDSW version 1.10.5. Best wishes, Salim ### **Description of the Docker Image** This Docker image is a **customized environment** tailored for Cloudera Data Science Workbench (CDSW) in an **air-gapped (offline)** setting. It includes the following components: 1. **Base Image**: - Starts with `docker.repository.cloudera.com/cdsw/engine:8` , ensuring compatibility with CDSW. 2. **Operating System**: - **Ubuntu 20.04 LTS**, a lightweight and stable Linux distribution. 3. **MySQL 8.0.4**: - A milestone release of MySQL, installed from pre-downloaded `.deb` packages (no internet required). 4. **Python 3.8.18**: - Compiled from source to ensure version compatibility. 5. **Node.js 22.16.0**: - Installed via a pre-extracted binary archive. 6. **Grafana Enterprise 11.6.0**: - Installed using a `.deb` package for enterprise-grade monitoring. 7. **Ollama**: - A pre-downloaded binary for running large language models locally. 8. **Python Packages**: - Installed **offline** from a pre-downloaded `requirements.txt` file and local wheels (`.whl` or `.tar.gz`) . 9. **Exposed Ports**: - MySQL (3306), Python apps (8000), Grafana (3000), and Ollama (11434). --- ### **Requirements to Build the Image** To build this image in an **air-gapped environment**, you must pre-download and include the following: 1. **Pre-downloaded Dependencies**: - **MySQL 8.0.4 `.deb` packages** (from Cloudera or MySQL archives). - **Python 3.8.18 source tarball** (from [python.org](https://www.python.org/ftp/python/3.8.18/)). - **Node.js 22.16.0 Linux x64 binary** (from [nodejs.org](https://nodejs.org/dist/v22.16.0/)). - **Grafana Enterprise 11.6.0 `.deb` package** (from Grafana’s enterprise download page). - **Ollama binary** (from [ollama.ai/download](https://ollama.ai/download)). 2. **Offline Python Packages**: - Use `pip download -r requirements.txt -d python_packages/` in an online environment to fetch all dependencies locally . 3. **Directory Structure**: Ensure the following files/directories exist in the build context: ```bash . ├── Dockerfile ├── requirements.txt ├── ollama # Pre-downloaded Ollama binary └── dependencies/ ├── mysql-8.0.4/ # MySQL .deb packages ├── python/ # Python 3.8.18 source ├── node-v22.16.0-linux-x64.tar.xz ├── grafana-enterprise-11.6.0.deb └── python_packages/ # Pre-downloaded Python wheels ``` 4. **Build Command**: Run: ```bash docker build -t custom-cdsw:latest . ``` 5. **Push to Private Registry (Optional)**: For CDSW integration, push the image to a registry accessible by CDSW: ```bash docker tag custom-cdsw:latest <your-registry>/custom-cdsw:latest docker push <your-registry>/custom-cdsw:latest ``` --- ### **Key References** - Docker images contain application code, libraries, tools, and dependencies . - Use `docker inspect` to view details about the image . - Dockerfiles are often shared in repositories for transparency . Let me know if you need further clarification!   ... View more

FYI you can use this site to set the password to something else: https://www.browserling.com/tools/bcrypt ... View more

Thanks Mike - I thought this was the case.  ... View more

@akshay0103  Could you please check with your account team of a new docker credentials or getting the existing one activated or create an administrative case.  ... View more

Hmm, that makes sense I suppose. That was my next guess 😉 Glad you figured it out, and thanks for posting the answer here, I appreciate it! ... View more

Hi Krishna We have done this by pushing commands out to the shell after setting up a trusted SSH connection between CDSW and the Unix server.   This is the python function we use: user_name = "username" unix_server = "my.unix.host" unix_path = "/some/path" file_to_transfer = "my_csv_file.csv" def scp_file_to_sas(local_path, file_name, user_name, unix_server, unix_path): p = subprocess.Popen( [ "scp", "-v", local_path + file_name, user_name + "@" + unix_server + ":/" + unix_path + "/" + file_name, ] ) sts = os.waitpid(p.pid, 0) ... View more

@asandovala21 Has the reply helped resolve your issue? If so, please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future. Thanks. ... View more

Hi, whichever user you log in as under the User Settings -> Hadoop Authentication should be what CDSW uses when accessing the rest of the cluster. Typically your CDSW username/password is your SSO login, but you can change this Hadoop Authentication settings if you want. Let me know if that works for you! ... View more