https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# rancher-desktop
a
This message was deleted.
w
whats the issue? assuming you got basic docker operations going?
b
hey Justin so whenever i reopen and rebuild dev container i get this error message i have these setting in my vscode settings.json { "dev.containers.mountWaylandSocket": false, "dev.containers.executeInWSL": true, "workbench.colorTheme": "Visual Studio Dark" }
i can share the output of the full logs?
w
so docker cli is working now right?
b
seems like it yes
using ubuntu however
i gave up on cmd
w
well than its not?
b
im using ubuntu rancher wsl remix for now
w
are you user ubuntu is not running dockerd?
b
moby im using as the container engine
w
what does 
docker info
show in ubuntu
the named pipe ACL wouldn't necessarily be solved by ubuntu, but they may be using TCP instead so bypassing
b
$ docker info Client: Version: 25.0.4-rd Context: default Debug Mode: false Plugins: buildx: Docker Buildx (Docker Inc.) Version: v0.13.0 Path: /home/.docker/cli-plugins/docker-buildx compose: Docker Compose (Docker Inc.) Version: v2.24.7 Path: /home/.docker/cli-plugins/docker-compose Server: Containers: 26 Running: 0 Paused: 0 Stopped: 26 Images: 9 Server Version: 25.0.3 Storage Driver: overlay2 Backing Filesystem: extfs Supports d_type: true Using metacopy: false Native Overlay Diff: true userxattr: false Logging Driver: json-file Cgroup Driver: cgroupfs Cgroup Version: 1 Plugins: Volume: local Network: bridge host ipvlan macvlan null overlay Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog Swarm: inactive Runtimes: runc io.containerd.runc.v2 Default Runtime: runc Init Binary: docker-init containerd version: 4e1fe7492b9df85914c389d1f15a3ceedbb280ac runc version: 51d5e94601ceffbbd85688df1c928ecccbfa4685 init version: Security Options: seccomp Profile: builtin Kernel Version: 5.15.146.1-microsoft-standard-WSL2 Operating System: Rancher Desktop WSL Distribution OSType: linux Architecture: x86_64 CPUs: 8 Total Memory: 7.647GiB Name: COMP0026082 ID: 808e27d7-4eb5-4bd2-b770-645b15bff28a Docker Root Dir: /var/lib/docker Debug Mode: false Experimental: false Insecure Registries: 127.0.0.0/8 Live Restore Enabled: false WARNING: No blkio throttle.read_bps_device support WARNING: No blkio throttle.write_bps_device support WARNING: No blkio throttle.read_iops_device support WARNING: No blkio throttle.write_iops_device support
w
because your machine is very oddly configured stuff will act weird
😁 1
and what does 
docker context ls
say
in ubuntu
given vscode is running in windows it will try and use docker.sock in windows
👀 1
b
interesting ok i think this is the issue then
w
interesting that socket works, but its bouncing from one distro via mnt to another distro (rancher-desktop)
i would still focus on getting docker working in windows. i think it will be very fragile if code needs to call ubuntu who needs to call back out to host to then call into rancher-desktop distro
b
fixing the pipe issue?
w
the docker extension can override some of the DOCKER_HOST stuff
the error you saw when running docker in CMD?
yes
b
any ideas where i can start?
w
//pipe/ <-
do the thing i mentioned which is getting your user in docker-users
and see if there is an ACL on the pipe like i mentioned in the other thread
again vscode will depend on docker in the host and maybe you can force it to use other things it will be somewhat fragile
b
no docker-user as ive gotten rid of docker and docker-desktop to use r-d and done a mega wipe of the machine im using to test r-d on
w
it wasn't a clean uninstall and the machine based RD install didn't update it.
now user based RD install (non-admin) uses a different socket in your user profile so it may have avoided the contention with your old install
the other possibility is your security software is blocking some access to pipes
b
i think i was a bit unclear before.... the computer was reimaged before we installed rancher, and since then docker desktop installer has not been run
👍 1
w
doesn't explain why you can't get to that pipe, but you need to run that powershell for me to have a guess at that
46 Views
Open in Slack
PreviousNext
Powered by