Week 1: Q&A Session

Docker on Windows can present unique challenges because it relies on virtualization technology that interacts with your specific hardware and Windows configuration. Here's a systematic approach to resolving common issues:

Ensuring Proper Installation Requirements:

• WSL 2 Configuration: Docker Desktop for Windows works best with WSL 2
  • Run wsl --update to ensure you have the latest WSL version
  • Verify WSL 2 is your default: wsl --set-default-version 2
• Virtualization: Ensure virtualization is enabled in BIOS/UEFI
  • Check Task Manager's Performance tab for "Virtualization: Enabled"
  • If disabled, restart computer and enter BIOS settings to enable it (often under Advanced Settings)
• Windows Features: Ensure required Windows features are enabled
  • Go to Control Panel → Programs → Windows Features
  • Enable: Hyper-V, Virtual Machine Platform, Windows Subsystem for Linux

Performance Issues:

• Resource Allocation: Docker Desktop may need more resources
  • Open Docker Desktop → Settings → Resources
  • Increase CPU allocation (at least 2 cores)
  • Increase Memory (at least 4GB for development work)
  • Adjust Swap size based on your needs
• Storage Location: WSL 2 storage location can affect performance
  • Consider moving WSL 2 to an SSD if available
  • Use wsl --export and wsl --import to relocate
• Volume Mounting: Windows and WSL paths can cause performance issues
  • Use WSL paths instead of Windows paths in volume mounts when possible
  • Add :cached or :delegated to volume mounts in docker-compose.yml

Network Issues:

• Firewall Interference: Windows Defender or other firewalls may block Docker networking
  • Check firewall settings and create exceptions for Docker
  • Temporarily disable firewall to test if it's the cause
• VPN Conflicts: VPN software can interfere with Docker networking
  • Disconnect from VPN temporarily to test
  • Configure VPN to allow local network traffic
• Docker Network Issues: Reset Docker networking when problems persist
  • Run docker network prune to remove unused networks
  • In extreme cases, reset Docker to factory defaults in Settings

Alternative Approach: If Docker Desktop continues to cause problems, consider running Python directly in WSL 2 without Docker for development. This provides many of the same benefits (Linux environment, isolation from Windows) with potentially fewer compatibility issues.

Real-world solution: In a recent project, we found that Docker Desktop performance was poor for team members using Windows. Our solution was to develop a hybrid approach: using Docker for running databases and services, but running the Python application directly in WSL 2 during development. This gave us the best of both worlds - containerized dependencies but native performance for the code we were actively changing.

Virtual environment issues can be frustrating because they create a disconnect between what you've installed and what your editor or interpreter can access. Let's diagnose and solve these common problems:

Understanding Virtual Environments:

Think of a virtual environment as a separate "room" for a Python project. Each room has its own set of packages, isolated from other rooms. VS Code needs to know which room to look in.

Common Issues and Solutions:

1. VS Code Not Detecting the Environment:
   • Problem: VS Code is using a different Python interpreter than your virtual environment
   • Solution:
     1. Press Ctrl+Shift+P and type "Python: Select Interpreter"
     2. Look for your virtual environment in the list (usually named "venv" or ".venv")
     3. If not visible, click "Enter interpreter path" and browse to the Python executable in your virtual environment:
        • Windows: venv\Scripts\python.exe
        • Mac/Linux: venv/bin/python
2. Terminal Not Using the Environment:
   • Problem: Your terminal hasn't activated the virtual environment
   • Solution:
     1. Manually activate the environment:
        • Windows: venv\Scripts\activate
        • Mac/Linux: source venv/bin/activate
     2. VS Code can auto-activate environments:
        • Add to settings.json: "python.terminal.activateEnvironment": true
3. Modules Still Not Found After Installation:
   • Problem: Packages installed in wrong environment or interpreter cache issues
   • Solution:
     1. Verify the active environment in your terminal (should show environment name in prompt)
     2. Confirm packages are installed in this environment: pip list
     3. If packages are missing, install them: pip install -r requirements.txt
     4. Restart VS Code or reload window: Ctrl+Shift+P → "Developer: Reload Window"
4. Multiple Python Versions Causing Confusion:
   • Problem: Multiple Python installations on your system conflict
   • Solution:
     1. Be explicit when creating environments: python3.10 -m venv venv
     2. In VS Code, select the specific interpreter path as mentioned earlier
     3. When running Python from terminal, use python -m module_name instead of direct execution to ensure the correct Python is used

Debugging Environment Issues:

When facing stubborn environment problems, try these diagnostic steps:

1. Check Current Environment: In your Python code, add:

   import sys
   print(sys.executable)  # Shows which Python is running
   print(sys.path)        # Shows where Python looks for modules

2. Verify Package Installation: In the terminal:

   pip show package_name  # Shows info about a specific package
   pip list                # Lists all installed packages

3. Check VS Code Environment Status: Look at the Python interpreter in the bottom status bar of VS Code - it should show your virtual environment name

Preventative Measures:

• Standardize Environment Locations: Always create virtual environments in the same relative location in your projects (e.g., always use ".venv" in the project root)
• Use Project-Specific Settings: Create a .vscode/settings.json file in your project to specify the Python path:

  {
      "python.defaultInterpreterPath": "${workspaceFolder}/.venv/bin/python",
      "python.terminal.activateEnvironment": true
  }

• Consider Environment Management Tools: Tools like Poetry or Pipenv can simplify environment management

Real-world practice: Many professional developers create a shell script or batch file called dev_setup.sh that creates the virtual environment, installs dependencies, and configures VS Code settings for a project. This ensures everyone on the team has an identical setup process.