Forem: kshitij Bhatnagar

How to Run DeepSeek R1 Locally (Using Ollama + ChatboxAI)

kshitij Bhatnagar — Thu, 20 Feb 2025 02:09:58 +0000

If you want to run DeepSeek R1 locally on your system, there's no need to worry. This guide is written in a simple and easy-to-follow manner, explaining step-by-step how to use Ollama and ChatboxAI to get it running.

🖥️ System Requirements (Based on GPU/RAM)

Each model has different hardware requirements, so first, check which model your system can support:

Model	GPU Required	VRAM (GPU Memory)	RAM (System Memory)	Storage (ROM)
DeepSeek R1 1.5B	No GPU / Integrated GPU	4GB+	8GB+	10GB+
DeepSeek R1 7B	GTX 1650 / RTX 3050	6GB+	16GB+	30GB+
DeepSeek R1 14B	RTX 3060 / RTX 4060	12GB+	32GB+	60GB+
DeepSeek R1 33B	RTX 4090 / A100	24GB+	64GB+	100GB+

👉 If your system has GTX 1650 or lower, you can only run DeepSeek R1 1.5B or at most 7B.
👉 For 7B, at least 16GB RAM is required.
👉 If you have a GPU lower than GTX 1650 (or an integrated GPU), only use 1.5B to avoid crashes.

⚙️ Step-by-Step Installation Guide

1️⃣ Install Ollama (Base for Llama Models)

Ollama is a lightweight tool that helps run LLMs (Large Language Models) locally. Install it first:

🔗 Ollama Installation Link

👉 For Windows Users:

Download the installer and install it (just click Next-Next).
Open CMD and check by running:

  ollama run llama2

If this command runs successfully, the installation is complete.

👉 For Mac Users:

Open Terminal and run:

curl -fsSL https://ollama.com/install.sh | sh

2️⃣ Download the DeepSeek R1 Model

Use the following command to pull the model:

ollama pull deepseek-ai/deepseek-coder:7b

- 👉 If you want to run 1.5B instead of 7B, use:

ollama pull deepseek-ai/deepseek-coder:1.5b

⚠ This download may take some time depending on your internet speed. Once downloaded, you can run it using Ollama.

3️⃣ Install ChatboxAI (Optional GUI for Better Experience)

If you want a Graphical User Interface (GUI), ChatboxAI is the best tool to interact with local AI models.

🔗 ChatboxAI Installation Link

Installation Steps:

Ensure Python 3.10+ is installed.
Open Command Prompt (CMD) and run:

git clone https://github.com/oobabooga/text-generation-webui.git
cd text-generation-webui
pip install -r requirements.txt

Start the server:

python server.py

Open your browser and go to localhost:7860, then select your model.

🚀 Running DeepSeek R1 (Final Step)

Once everything is installed, it’s time to run the model:

👉 Open CMD and run:

ollama run deepseek-ai/deepseek-coder:7b

👉 If 7B is not running, try with 1.5B:

ollama run deepseek-ai/deepseek-coder:1.5b

👉 If you are using ChatboxAI, just open the browser and interact with the model through the GUI.

Now you can use DeepSeek R1 for coding, AI chat, and optimizing your workflow! 😎🔥

🛠️ Common Problems & Solutions

❌ 1️⃣ Model crashes due to low VRAM?
✔ Try 1.5B instead of 7B.
✔ Increase Windows Pagefile (Virtual Memory settings).

❌ 2️⃣ Model response is too slow?
✔ Use SSD instead of HDD.
✔ Close background applications.
✔ Optimize RAM usage.

❌ 3️⃣ ‘Command not found’ error in CMD?
✔ Check if Ollama is installed correctly.
✔ Ensure Python and dependencies are installed.

🤩 Conclusion

If you followed this guide correctly, you can now run DeepSeek R1 locally without relying on third-party APIs. This is a privacy-friendly and cost-effective solution, perfect for developers and freelancers.

If you face any issues, drop a comment, and you’ll get help! 🚀🔥

Manage Multiple GitHub Accounts with SSH Keys

kshitij Bhatnagar — Wed, 21 Aug 2024 23:51:03 +0000

In today's dynamic development environment, it's common to juggle multiple GitHub accounts—whether for work, personal projects, or open-source contributions. However, seamlessly switching between your office and personal GitHub profiles can be challenging if not properly managed. This guide will walk you through the best practices and essential steps to effortlessly handle multiple GitHub accounts, ensuring that your workflows remain smooth and your code stays organized, no matter which account you’re using.

Step-by-Step Guide

1. Generate SSH Keys

Generate separate SSH keys for your office and personal GitHub accounts.

Office Account:

ssh-keygen -t rsa -b 4096 -C "your_office_email@example.com" -f ~/.ssh/id_rsa_office

Personal Account:

ssh-keygen -t rsa -b 4096 -C "your_personal_email@example.com" -f ~/.ssh/id_rsa_personal_account

2. Add SSH Keys to GitHub

Office Account:

Copy the public key to your clipboard:

    cat ~/.ssh/id_rsa_office.pub

Go to GitHub (office account) -> Settings -> SSH and GPG keys -> New SSH key.
Paste the public key and save.

Personal Account:

Copy the public key to your clipboard:

    cat ~/.ssh/id_rsa_personal_account.pub

Go to GitHub (personal account) -> Settings -> SSH and GPG keys -> New SSH key.
Paste the public key and save.

3. Configure SSH Agent

Start the SSH agent and add your keys.

eval "$(ssh-agent -s)"
ssh-add ~/.ssh/id_rsa_office
ssh-add ~/.ssh/id_rsa_personal_account

4. Configure `~/.ssh/config`

Edit your ~/.ssh/config file to define aliases for your office and personal GitHub accounts.

#### Configuration for office account
Host github.com
    HostName github.com
    User git
    IdentityFile ~/.ssh/id_rsa_office
    IdentitiesOnly yes

#### Configuration for personal account
Host github.com-personal-account
    HostName github.com
    User git
    IdentityFile ~/.ssh/id_rsa_personal_account
    IdentitiesOnly yes

5. Clone Repositories

Clone repositories using the appropriate alias to ensure the correct SSH key is used.

Office Repository:

git clone git@github.com:organization/repository.git

Personal Repository:

git clone git@github.com-personal-account:username/repository.git

6. Verify Remote URLs

Check the remote URLs to ensure they are set correctly.

git remote -v

This should show URLs that match the aliases defined in your ~/.ssh/config.

7. Push and Pull Changes

When pushing or pulling changes, Git will automatically use the correct SSH key based on the repository URL.

Push Changes:

git push origin main

Pull Changes:

git pull origin main

Summary of the steps

Generate SSH Keys: Create separate SSH keys for your office and personal GitHub accounts.
Add SSH Keys to GitHub: Add the public keys to the respective GitHub accounts.
Configure SSH Agent: Start the SSH agent and add the generated keys.
Edit ~/.ssh/config: Define aliases for your office and personal accounts, specifying the correct IdentityFile for each.
Clone Repositories: Use the appropriate alias in the repository URL to ensure the correct key is used.
Verify Remote URLs: Ensure the remote URLs are set correctly to match the aliases.
Push and Pull Changes: Git will use the correct SSH key based on the repository URL.

By following these steps, you can seamlessly manage multiple GitHub accounts with different SSH keys, ensuring the correct key is used for each repository.

The best part is that after configuring your ~/.ssh/config file and carefully cloning repositories using the correct aliases, you won’t need to worry about managing the SSH agent during push and pull operations. Git will automatically select the appropriate SSH key based on the repository's URL, making your workflow seamless and hassle-free.

Forem: kshitij Bhatnagar

How to Run DeepSeek R1 Locally (Using Ollama + ChatboxAI)

🖥️ System Requirements (Based on GPU/RAM)

⚙️ Step-by-Step Installation Guide

1️⃣ Install Ollama (Base for Llama Models)

👉 For Windows Users:

2️⃣ Download the DeepSeek R1 Model

3️⃣ Install ChatboxAI (Optional GUI for Better Experience)

🤩 Conclusion

Manage Multiple GitHub Accounts with SSH Keys

Step-by-Step Guide

1. Generate SSH Keys

Office Account:

Personal Account:

2. Add SSH Keys to GitHub

Office Account:

Personal Account:

3. Configure SSH Agent

4. Configure ~/.ssh/config

5. Clone Repositories

Office Repository:

Personal Repository:

6. Verify Remote URLs

7. Push and Pull Changes

Push Changes:

Pull Changes:

Summary of the steps

4. Configure `~/.ssh/config`