rancher-users #rancher-desktop

Join the conversation Join Slack

rancher-desktop

quick-keyboard-83126

06/29/2022, 8:36 PM

Hello world... I'd like to chase down:

quick-keyboard-83126

06/29/2022, 8:49 PM

So, I'd like to use

docker buildx build

to chain build dependencies, but apparently in order to do that, i need to use

--push

, but I don't really want to publish to a remote registry, so I tried using:

docker run -d -p 5001:5000 --restart=always --name registry registry:2

(port 5000 is in use by

Server: AirTunes/615.12.1

) But (once I pick my non localhost ip address...), this fails miserably with:

error: failed to solve: failed to do request: Head "https://<my-non-localhost-ip>:5001/v2/foo/blobs/sha256:<random-sha>": http: server gave HTTP response to HTTPS client

I understand that

registry

speaks

http

out of the box and

docker

wants to speak

https

. I get that there's a file I could change (but, I suspect that I'd have to change it in my.

lima vm

, and that doing this would be arguably very dangerous). Anyone have suggestions?

quick-keyboard-83126

06/29/2022, 9:23 PM

Can I get someone to add some items to this epic: https://github.com/rancher-sandbox/rancher-desktop/issues/2406 • https://github.com/rancher-sandbox/rancher-desktop/issues/2473 • https://github.com/rancher-sandbox/rancher-desktop/issues/2474

nutritious-application-85076

06/30/2022, 9:45 AM

Is there a way from a terminal to push an image to the VM as we can do with

kind load docker-image ...

or the only way to achieve that is to add an image using the UI ?

nutritious-application-85076

06/30/2022, 10:13 AM

I have an issue using

nerdctl

. Where can I post my question ?

clever-winter-66704

07/03/2022, 3:32 AM

Hello everyone, I'm trying to get mimic what minikube tunnel performs with rancher desktop to access webpage using a nodeport (istio-gateway) any

nutritious-application-85076

07/05/2022, 12:00 PM

Is there a way to troubleshoot a traefix ingress route as I got an error

http 404

? I can access the service using

kubectl port-foward

and address

<http://localhost:7007/catalog>

rapid-traffic-3855

07/05/2022, 3:30 PM

some folks in my organization suggested to downgrade rancher desktop from v1.4.1 is there any documentation where i can follow the steps to downgrade rancher desktop version ?

rough-house-44159

07/05/2022, 6:56 PM

I have been looking for documentation to connect docker cli with Rancher-desktop daemon running in WSL-moby I don't have linux based machine or macbook. Creating complex scenarios for me to deal with So, i have been tryin to set up something like this

wsl -l

1. Debian 2. Rancher-desktop 3. Rancher-desktop-data How can I connect docker from debian? I couldn't locate any doc. Also how can I transfer kube config to talk to k3s clusters? Have tried different k3s image versions. Right now, I am on stable one and wsl integration only works in achieving integration with the host system. Please advice. Thank you

victorious-architect-31541

07/06/2022, 8:39 AM

hi, nobody uses rancher desktop with nerdctl on Mac with Ansible molecule? I would like to substitute the docker driver with the rancher desktop, but it complains it cannot find the docker unix thing

faint-pizza-17848

07/06/2022, 10:30 AM

Hello apologies if this has been asked before, but I am trying to find the location to configure the proxy settings for Rancher Desktop. Could any please help?

colossal-minister-18571

07/06/2022, 10:02 PM

Went running Rancher Desktop on Windows is SLE Micro running in WSL2? If not, what is running in WSL2?

miniature-belgium-38783

07/07/2022, 2:40 PM

Hi Team I have installed Rancher Desktop Version: 1.4.1 on MacBookPro16,1 intel MacOs 12.4 Before that i had Docker Desktop installed , working with portainer with no problem Now it doesn't work This is the docker-compose.yml

version: '3'

volumes:
  portainer-data:
    external: true


services:
  portainer:
    image: portainer/portainer-ce:2.9.3
    container_name: portainer
    restart: unless-stopped
    security_opt:
      - no-new-privileges:true
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - /var/run/docker.sock:/var/run/docker.sock
      - portainer-data:/data
    ports:
      - 9443:9443

My guess is that its related to docker.sock , the docker doesn't receive the permission to it please Advise

sticky-art-85060

07/11/2022, 10:16 AM

hi all ... i have a very basic question ... why all my pods are hang in ContainerCreating ... where can I check for the local issue? $kubectl -n kube-system get pods NAME READY STATUS RESTARTS AGE local-path-provisioner-6c79684f77-lk6x7 0/1 ContainerCreating 0 110s helm-install-traefik-pfml6 0/1 ContainerCreating 0 110s helm-install-traefik-crd-8skws 0/1 ContainerCreating 0 110s coredns-d76bd69b-nc2q7 0/1 ContainerCreating 0 110s metrics-server-7cd5fcb6b7-mr99d 0/1 ContainerCreating 0 110s

adventurous-insurance-41443

07/11/2022, 5:18 PM

I wrote a

compose.yaml

file that looks like

version: "3.8"
services:
  app:
    build:
      context: .
      dockerfile: local.Dockerfile
    ports:
      - "80:8000"
    environment:
      ENVIRONMENT_NAME: "LOCAL"
      BUNCH_O_ENVIRONMENT_VARS: "HERE"
    restart: always
    volumes:
      - .:/root/work

and it builds the container successfully and then when it starts the container i get

app_1 |time="2022-07-11T17:03:16Z" level=fatal msg="failed to open \"/var/lib/nerdctl/dbb19c5e/containers/default/e8ec1111f96eda2b4ea51192a641fdb9ceaaa2b4550afe95eb17de8c8cacb2bb/e8ec1111f96eda2b4ea51192a641fdb9ceaaa2b4550afe95eb17de8c8cacb2bb-json.log\", container is not created with `nerdctl run -d`?: stat /var/lib/nerdctl/dbb19c5e/containers/default/e8ec1111f96eda2b4ea51192a641fdb9ceaaa2b4550afe95eb17de8c8cacb2bb/e8ec1111f96eda2b4ea51192a641fdb9ceaaa2b4550afe95eb17de8c8cacb2bb-json.log: no such file or directory"

and indeed

/var/lib/nerdctl

is missing from my computer. I am running macOS, and it appears to me that

/var/lib

is read-only.

👀 1

agreeable-refrigerator-81827

07/11/2022, 5:20 PM

Wondering if anyone here was successfully able to install Project Falco on Rancher Desktop? I can see that the Image Type for the Rancher Desktop nodes is Alpine Linux. Does that mean I can proceed with the Linux Generic (Binary Package) installer for Falco? https://falco.org/docs/getting-started/installation/

clever-guitar-78476

07/12/2022, 3:43 AM

any support person ?? or anyone help me to resolve rancher-desktop installation issue

rhythmic-umbrella-94086

07/13/2022, 4:54 PM

@fast-garage-66093 I had a load of trouble getting RD to run on a fresh install. Turned out old ~/.docker settings from having run Colima in the past were messing things up. Might be good to put something in the FAQ about that.

thousands-mechanic-72394

07/13/2022, 7:30 PM

moved to #k3s

elegant-memory-40145

07/13/2022, 9:32 PM

Is there any way to install Rancher Desktop without an internet connection? If not is there a feature request to allow users to do this? Thanks!

elegant-rose-89654

07/14/2022, 7:21 AM

Hi everyone. I wonder if someone can help me with a little debugging. I have Rancher 2.6.3 and today my RKE cluster is unavailable (albeit the applications are working and responding). The message I see is

Cluster agent is not connected

. Can someone tell me how to debug this? Thank you

ripe-grass-75099

07/14/2022, 1:28 PM

hi - I'm using Rancher Desktop on windows (1.4.1) and am having weird problems with docker build. It can find google.com from within the container but not api.nuget.org. The ping works fine from the host OS.

FROM <http://mcr.microsoft.com/dotnet/sdk:6.0-alpine|mcr.microsoft.com/dotnet/sdk:6.0-alpine>
#RUN ping <http://google.com|google.com>
RUN ping <http://api.nuget.org|api.nuget.org>

and the output

C:\temp\docker>docker build .
Sending build context to Docker daemon  2.048kB
Step 1/4 : FROM <http://mcr.microsoft.com/dotnet/sdk:6.0-alpine|mcr.microsoft.com/dotnet/sdk:6.0-alpine>
 ---> 68f959202edb
Step 2/4 : RUN ping <http://api.nuget.org|api.nuget.org>
 ---> Running in 190474634dc2
ping: bad address '<http://api.nuget.org|api.nuget.org>'
The command '/bin/sh -c ping <http://api.nuget.org|api.nuget.org>' returned a non-zero code: 1

A curl in the docker build returns this:

% Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0* Could not resolve host: <http://api.nuget.org|api.nuget.org>
* Closing connection 0
curl: (6) Could not resolve host: <http://api.nuget.org|api.nuget.org>

Really not sure what is going on as other addresses appear to work fine so it shouldn't be a networking issue, but everything suggests it is

witty-honey-18052

07/14/2022, 2:58 PM

I feel a bit silly for asking, and I've searched here and github, is there an issue with the included rancher dashboard with RD on Windows? I'm on 1.4.1 and don't see a way to launch or enable the dashboard

elegant-memory-40145

07/14/2022, 4:55 PM

Rancher Desktop offline installation / initialization. I copied the files in $HOME/AppData/Local/rancher-desktop/cache , $HOME/.kuberlr and the executable. The installation ran correctly and finished, I rebooted and when RD starts it fails with an wsl error message 4294967295. Taking a look at the .kube config file it is completely blank. Seems like it would start successfully if it had a valid config file. Any ideas>?

ripe-grass-75099

07/15/2022, 1:25 PM

i know this is a docker build thing but I'm curious as to why I get this warning when using rancher desktop as my docker host but not docker desktop? (WSL2.0) and is there a way to supress it when using Rancher?

SECURITY WARNING: You are building a Docker image from Windows against a non-Windows Docker host. All files and directories added to build context will have '-rwxr-xr-x' permissions. It is recommended to double check and reset permissions for sensitive files and directories.

ripe-grass-75099

07/15/2022, 2:41 PM

This may be a stupid question considering it's open source but I have 3 kubectl contexts on my PC (one local, handled by Rancher, the others AWS). I can start rancher desktop which fires up my local K8S instance and I can switch context in the rancher desktop toolbar to an AWS one but when I start the "Rancher K8S dashboard" this keeps using the local cluster. Is using a remote cluster not supported in this edition?

many-plastic-16454

07/15/2022, 10:40 PM

I'm using Rancher Desktop 1.4.1 on M1 Mac, and using Moby. I'm just trying to connect to the host application from container. I think I'm missing something super simple. I run

docker run -it --rm --add-host=host.docker.internal:host-gateway debian:latest bash

and on the host side, I'm running

python3 -m http.server 9876

. So on the container, I installed telnet and

telnet host.docker.internal 9876

but unable to connect. What am I missing?

adventurous-insurance-41443

07/18/2022, 2:14 PM

Do I need to completely uninstall Docker Desktop before installing Rancher Desktop?

crooked-rocket-3338

07/18/2022, 3:32 PM

Hi guys, I was running rancher desktop using

containerd

nerdctl

successfully, now I switched to `moby`/`docker` and my mount (bind) are failing. (win11 / WSL2 / rancher desktop 1.4.1). I read a lot a related issues about that but cannot find a workaround does anyone have a lead for me ? To reproduce :

docker run --mount type=bind,source=/etc/passwd,target=/etc/passwd --rm ubuntu:20.04

Returns:

docker: Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error mounting "/mnt/wsl/rancher-desktop/run/docker-mounts/6b17adac-3323-46ab-933a-202faa10537a" to rootfs at "/etc/passwd": mount /mnt/wsl/rancher-desktop/run/docker-mounts/6b17adac-3323-46ab-933a-202faa10537a:/etc/passwd (via /proc/self/fd/6), flags: 0x5001: not a directory: unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type.

adventurous-insurance-41443

07/18/2022, 4:48 PM

I have a compose file that successfully boots up a container when I run

nerdctl compose up --build

. The webserver in the container is running without error. But when I try to hit it with a HTTP message, I get error

Error: connect ECONNREFUSED 127.0.0.1:8556

. (details in thread)

Title

adventurous-insurance-41443

07/18/2022, 4:48 PM

I have a compose file that successfully boots up a container when I run

nerdctl compose up --build

. The webserver in the container is running without error. But when I try to hit it with a HTTP message, I get error

Error: connect ECONNREFUSED 127.0.0.1:8556

. (details in thread)

compose.yaml:

networks:
  default:
    name: my-network
services:
  appllnamell:
    build:
      context: .
      dockerfile: local.Dockerfile
    ports:
      - "8556:8000"
    environment:
      AUDITLOG_S3_BUCKET: "some-value"
      AND_OTHER_ENV_VARS: "have been censored"
    restart: always
    volumes:
      - .:/root/work

The output shows that things are working and the gunicorn server is sitting and waiting for responses:

zsh ❯ nerdctl compose up --build
WARN[0000] build.config should be relative path, got "/Users/my.name/repos/my-repo"
WARN[0000] Ignoring: volume: Bind: [CreateHostPath]
WARN[0000] found 3 orphaned containers: [0xc0001b6460 0xc0001b6540 0xc0001b6620], you can run this command with the --remove-orphans flag to clean it up
INFO[0000] Building image my-repo_appllnamell
[+] Building 65.0s (12/12) FINISHED
 => [internal] load .dockerignore                                                                                                                                                                                                                        0.1s
 => => transferring context: 2B                                                                                                                                                                                                                          0.1s
 => [internal] load build definition from local.Dockerfile                                                                                                                                                                                               0.1s
 => => transferring dockerfile: 1.66kB                                                                                                                                                                                                                   0.1s
 => [internal] load metadata for <http://docker.internal.company.com/image-name:2018.08.01.cb601300ab|docker.internal.company.com/image-name:2018.08.01.cb601300ab>                                                                                                                                          0.5s
 => [1/7] FROM <http://docker.internal.company.com/image-name:2018.08.01.cb601300ab@sha256:101e6aa1c5f1f9100000d0b84b719ebc6029e53d048ecf5988e257acb4669d2b|docker.internal.company.com/image-name:2018.08.01.cb601300ab@sha256:101e6aa1c5f1f9100000d0b84b719ebc6029e53d048ecf5988e257acb4669d2b>                                                                                    0.1s
 => => resolve <http://docker.internal.company.com/image-name:2018.08.01.cb601300ab@sha256:101e6aa1c5f1f9100000d0b84b719ebc6029e53d048ecf5988e257acb4669d2b|docker.internal.company.com/image-name:2018.08.01.cb601300ab@sha256:101e6aa1c5f1f9100000d0b84b719ebc6029e53d048ecf5988e257acb4669d2b>                                                                                    0.0s
 => [internal] load build context                                                                                                                                                                                                                        0.0s
 => => transferring context: 78B                                                                                                                                                                                                                         0.0s
 => CACHED [2/7] WORKDIR /root/work                                                                                                                                                                                                                      0.0s
 => CACHED [3/7] COPY requirements-dev.txt .                                                                                                                                                                                                             0.0s
 => CACHED [4/7] COPY requirements.txt .                                                                                                                                                                                                                 0.0s
 => CACHED [5/7] RUN pip install -r requirements-dev.txt                                                                                                                                                                                                 0.0s
 => CACHED [6/7] RUN apt-get update --allow-releaseinfo-change                                                                                                                                                                                           0.0s
 => CACHED [7/7] RUN apt-get install --yes curl                                                                                                                                                                                                          0.0s
 => exporting to oci image format                                                                                                                                                                                                                       64.2s
 => => exporting layers                                                                                                                                                                                                                                  0.0s
 => => exporting manifest sha256:4ee254513594a1fde0b31ad2d02a6a4d3c6483f6466f087f16de83f61f74b0ff                                                                                                                                                        0.0s
 => => exporting config sha256:59c277a3c93b664ca8e31c4699689bf2bb29673c97ea5c27607b52f46972cafc                                                                                                                                                          0.0s
 => => sending tarball                                                                                                                                                                                                                                  64.1s
unpacking <http://docker.io/library/risk-otb-eligibility_appllnamell:latest|docker.io/library/risk-otb-eligibility_appllnamell:latest> (sha256:4ee254513594a1fde0b31ad2d02a6a4d3c6483f6466f087f16de83f61f74b0ff)...done
INFO[0065] Creating container my-repo_appllnamell_1
INFO[0067] Attaching to logs
appllnamell_1 |[2022-07-18 16:45:18 +0000] [1] [INFO] Starting gunicorn 19.9.0
appllnamell_1 |[2022-07-18 16:45:18 +0000] [1] [INFO] Listening at: <http://0.0.0.0:8000> (1)
appllnamell_1 |[2022-07-18 16:45:18 +0000] [1] [INFO] Using worker: gthread
appllnamell_1 |[2022-07-18 16:45:18 +0000] [9] [INFO] Booting worker with pid: 9
appllnamell_1 |[2022-07-18 16:45:18 +0000] [11] [INFO] Booting worker with pid: 11

crooked-rocket-3338

07/18/2022, 4:53 PM

can you reach it with the IP of the WSL VM ? (to know the IP run

ip -c -o -br addr | grep eth0

in a wsl terminal). It happens to me time to time, that

localhost

do not fallback to the linux VM ...

adventurous-insurance-41443

07/18/2022, 4:53 PM

~~What is wsl?~~

I’m using macOS.

crooked-rocket-3338

07/18/2022, 4:55 PM

Haa ok forget about WSL then.

👍 1

adventurous-insurance-41443

07/19/2022, 2:21 PM

@fast-garage-66093 Any ideas of what is going on here or how I could get more info to help diagnose this issue? Thanks!

fast-garage-66093

07/19/2022, 4:48 PM

Not sure, first thing to try would be to make sure that the port is open inside the VM, so run something like

rdctl shell curl -k <https://localhost:8556>

View count: 11