melodic-agent-86823
02/15/2023, 9:42 AMstale-microphone-34763
02/15/2023, 3:09 PMmillions-zoo-61685
02/15/2023, 3:32 PMwide-river-75558
02/15/2023, 3:43 PMstale-island-29099
02/15/2023, 3:54 PMstocky-controller-14929
02/15/2023, 4:03 PMshy-megabyte-75492
02/15/2023, 8:54 PMdamp-daybreak-95993
02/16/2023, 2:26 AMdamp-daybreak-95993
02/16/2023, 2:39 AMnerdctl run --rm --gpus all nvidia/cuda:12.0.1-devel-ubuntu22.04 nvidia-smi
I get
With dockerd, using docker run --rm --gpus all nvidia/cuda:12.0.1-devel-ubuntu22.04 nvidia-smi
I get ocker: Error response from daemon: could not select device driver "" with capabilities: [[gpu]].
. If I tell it to use the nvidia runtime with -runtime=nvidia
it fails with ocker: Error response from daemon: Unknown runtime specified nvidia.
.
I'm using W11 with WSL2. It's a clean install. My GPU is a GTX 1080, and I have installed the latest drivers.
Cuda does work in WSL (without containers) as executing nvidia-smi
in my OpenSUSE-Tumbleweed in WSL returns the GPU info as expected.
Thu Feb 16 02:36:25 2023
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 525.89.02 Driver Version: 528.49 CUDA Version: 12.0 |
|-------------------------------+----------------------+----------------------+
| GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
| | | MIG M. |
|===============================+======================+======================|
| 0 NVIDIA GeForce ... On | 00000000:01:00.0 On | N/A |
| 31% 50C P0 42W / 200W | 966MiB / 8192MiB | 1% Default |
| | | N/A |
+-------------------------------+----------------------+----------------------+
shy-megabyte-75492
02/16/2023, 4:50 PMnerdctl build --tag helloworld:v1.0 .
with a dockerfile that is super simple, just get alpine. When I run a nerdctl pull alpine it works fine but I keep getting
ERROR [internal] load metadata for <http://docker.io/library/alpine:latest|docker.io/library/alpine:latest>
...
error: failed to solve alpine failed to do request .. dial tcp <ip> i/o timeout
FATA[0030] unrecognized image format
stocky-dream-23501
02/17/2023, 1:00 AMstocky-dream-23501
02/17/2023, 2:18 AMquick-keyboard-83126
02/17/2023, 10:27 AMbulky-coat-85959
02/17/2023, 1:50 PMcareful-mouse-48712
02/17/2023, 3:41 PMhundreds-actor-42498
02/18/2023, 4:42 PMlittle-horse-77834
02/19/2023, 3:59 AMYour kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap.
The same docker-compose.yml works with regular docker-compose using podman.orange-truck-53690
02/20/2023, 2:45 AMfuture-night-11133
02/20/2023, 5:46 AMFATA[0000] unsupported restart policy "unless-stopped", supported policies are: []
Doing some investigation at nerdctl code, I found this lines at checkRestartCapabilities:
res, err := client.IntrospectionService().Plugins(ctx, []string{"id==restart"})
if err != nil {
return false, err
}
if len(res.Plugins) == 0 {
return false, fmt.Errorf("no restart plugin found")
}
restartPlugin := res.Plugins[0]
capabilities := restartPlugin.Capabilities
if len(capabilities) == 0 {
capabilities = []string{"always"}
}
if !strutil.InStringSlice(capabilities, policySlice[0]) {
return false, fmt.Errorf("unsupported restart policy %q, supported policies are: %q", policySlice[0], restartPlugin.Capabilities)
}
It seems it could’t find the policies available from containerd so it set default to “always” only, which is the only one working here.
After some research, I came across this command to list containerd plugins:
ctr plugins ls
So I tried:
❯ rdctl shell ctr plugins ls
qemu-x86_64: Could not open '/lib64/ld-linux-x86-64.so.2': No such file or directory
Error: exit status 255
Is this a containerd problem, or rancher-desktop? Maybe because of M1 architecture.
@fast-garage-66093 maybe you have a clue about it.
Thanks!kind-gold-42406
02/20/2023, 8:43 AMkind-gold-42406
02/20/2023, 8:43 AMnice-toddler-37804
02/20/2023, 1:31 PMrancher-desktop-wsl-vm
and rancher-desktop
code are available here:
• rancher-desktop
• rancher-desktop-wsl-distro
My solution is based on a software named moproxy
, a software installed on WSL that handles the connections and transmissions of packets to an http proxy. The traffic from the network interface is redirected to moproxy
using iptables
, so any type of filtering on ports/address is supported.
I also made changes to the rancher-desktop graphical interface to make the proxy configurable from the rancher-desktop settings page or during the first run. Changes on the proxy configuration take effect immediately without needing a backend restart like the other change in settings.
I saw that recently there has been some activity on the Github issues to port the network stack to work with gvisor-tap-vsock
. I didn't saw any communication on that subject on the slack channel and didn't had the chance to manifest my interest in participating.
This issue is related to the problem I was working on and make the work I started useless as it also aims to bring proxy support. I would be happy to contribute to the effort and work on this issue if you let me know where to start. Thank you !incalculable-ghost-55080
02/22/2023, 12:35 PMbrew install --cask rancher
open -a Rancher\ Desktop
# Click allow admin access in appeared window
rdctl api /v0/settings --method PUT --body '{"kubernetes": {"enabled": false, "containerEngine": "moby", "memoryInGB": 8, "numberCPUs": 4}, pathManagementStrategy": "manual"}'
But yes, the above script does not work, since the essential things are loaded at the first start. Do I understand correctly that the only right way to do this with the RD installer? Ref
Thank you in advance!narrow-france-80098
02/22/2023, 5:06 PMsteep-journalist-13696
02/22/2023, 9:48 PMhappy-airport-88564
02/23/2023, 3:32 PMacceptable-guitar-10846
02/23/2023, 9:02 PMbored-farmer-36655
02/23/2023, 9:04 PMfuture-night-94031
02/24/2023, 9:59 AMError: unable to verify the first certificate
client-key-data: LS0tLS1CRUdJTiBFQyBQUklWQVRFIEtFWS0tLS0tCk1IY0NBUUVFSUNTMVlSOU9TTFllQzYyZHdEWk9GTnpldFJqRHY5c1RseWlGaTQzL0hySTFvQW9HQ0NxR1NNNDkKQXdFSG9VUURRZ0FFZnZCVFFTbFl3WHEzOUtIdlg4ZFk2VXVUMFVENEdXQ0o3UTJ3eDBNcTVQeUdTUGlOWWovawpKR3JuaGVRaFdKOGV4dkpZbHJLd2RPVUdJMndyVThKUzZ3PT0KLS0tLS1FTkQgRUMgUFJJVkFURSBLRVktLS0tLQo=
2023-02-24T09:57:36.250Z: Error starting lima: Error: unable to verify the first certificate
at TLSSocket.onConnectSecure (node:_tls_wrap:1530:34)
at TLSSocket.emit (node:events:390:28)
at TLSSocket._finishInit (node:_tls_wrap:944:8)
at TLSWrap.ssl.onhandshakedone (node:_tls_wrap:725:12) {
code: 'UNABLE_TO_VERIFY_LEAF_SIGNATURE'
}
I tried deleting the .kube
directory as well stil it doesn't work. What should I do?powerful-elephant-25838
02/24/2023, 10:11 AM