Install Docker and Kubernetes on Windows Subsystem for Linux (WSL). No Docker Desktop Required!

Поделиться
HTML-код
  • Опубликовано: 27 дек 2024

Комментарии • 26

  • @Dotphil01
    @Dotphil01 Год назад +2

    Great video. After following your steps on installing docker, I tried running the sudo docker ps -a command but kept getting an error message like this "Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?". How do I resolve this?

    • @BlaizeTech
      @BlaizeTech  Год назад

      Set your DOCKER_HOST environment variable to the IP address of your WSL2 instance. You can get this by typing ifconfig.

  • @khamarchaitanya
    @khamarchaitanya 15 дней назад

    In windows features didn't show containers option , other two options are there. if i follow your steps,shows error while installing docker. Plz Help

    • @BlaizeTech
      @BlaizeTech  15 дней назад

      I think you need a pro version.

  • @rcubickmprt
    @rcubickmprt 11 месяцев назад

    hai, great video.
    can my node in other vm join as worker to kubernetes in wsl with these settings?

    • @BlaizeTech
      @BlaizeTech  11 месяцев назад

      It's possible. This is just using MiroK8S, which allows you to create clusters.

    • @rcubickmprt
      @rcubickmprt 11 месяцев назад

      @@BlaizeTech Thank you for the quick response. I'm eager to follow the steps outlined for setting up Kubernetes on an on-premise Windows server as the master. I have an additional server that I'd like to join as a node to the master, Is it possible?

    • @BlaizeTech
      @BlaizeTech  11 месяцев назад

      @@rcubickmprtI don't think windows as a master is going to work. I've never seen such a setup, and I wouldn't recommend it even if it does work. Using Windows worker nodes is fine for Windows containers. If it has to be on Windows, WSL is your tool, although the WSL networking is not great. I would suggest using Linux as much as possible, and use Windows when necessary if at all.

    • @rcubickmprt
      @rcubickmprt 11 месяцев назад

      @@BlaizeTech
      Unfortunately, it has to be on Windows due to compatibility issues with other apps. By the way, I have the following devices:
      - 1 unit Windows Server
      - 2 unit Synology NAS
      In your opinion, if I have to use Kubernetes, where should I configure the master?
      and then Which is better, configuring it on WSL or using a VM and installing a Linux distribution?

    • @BlaizeTech
      @BlaizeTech  11 месяцев назад

      @@rcubickmprtI'd use a VM if you can. WSL is really more of dev tool, and the IO on the file system is slow. I prefer Ubuntu for MicroK8S because it's easy to install for small uses. You may wan to check out Rancher OS, too. It's more of a turnkey solution for Kubernetes.

  • @whiteking80
    @whiteking80 9 месяцев назад

    Great video. Imfollowing this tutoril step by step. However I notice following command which to open docker .service found none searching for the port. The latter script service has bit different than the the one you're demonstrating. May i know the alternative to find the port ?
    sudo nano /lib/systemd/system/docker.service

    • @whiteking80
      @whiteking80 9 месяцев назад

      sudo ss -tln | grep ':2375' found no response

    • @whiteking80
      @whiteking80 9 месяцев назад +1

      owh i just noticed you actually added and modify the script. Thanks 4 your video. Appreciate it.!

    • @BlaizeTech
      @BlaizeTech  9 месяцев назад +1

      @@whiteking80 Glad you found the solution.

    • @Marhaenism1930
      @Marhaenism1930 9 месяцев назад +1

      ah i thought was only me had same issue like that, because we werent using same OS as vid. glad it was solved

  • @rochesterbrad
    @rochesterbrad 4 месяца назад

    How do we deal with proxy server in way of doctor.
    Where do we add a cert pem file?

    • @BlaizeTech
      @BlaizeTech  4 месяца назад

      Here's how to handle this with the docker daemon.
      docs.docker.com/config/daemon/proxy/

  • @BioByMrKhaled
    @BioByMrKhaled 11 месяцев назад

    sudo systemctl daemon-reload
    System has not been booted with systemd as init system (PID 1). Can't operate.
    Failed to connect to bus: Host is down

    • @BlaizeTech
      @BlaizeTech  11 месяцев назад

      This happens because of older versions of WSL or Ubuntu. Make sure you've upgraded your WSL install (wsl --udpdate) and use a more current version of Ubuntu.

  • @Hellbending
    @Hellbending 10 месяцев назад +1

    Scoop > chocolatey 😉

    • @BlaizeTech
      @BlaizeTech  10 месяцев назад

      I'm old school. 😂😂

    • @Hellbending
      @Hellbending 10 месяцев назад +1

      @@BlaizeTech Hey… hey now - Git’s pretty old school? 😂😂

    • @BlaizeTech
      @BlaizeTech  10 месяцев назад

      @@Hellbending Ahh Yeah!!!