billowy-flag-37369
06/17/2022, 3:48 PMbrave-rocket-28538
06/17/2022, 10:04 PMgreen-restaurant-60209
06/18/2022, 2:26 PMquick-keyboard-83126
06/19/2022, 2:56 AMorange-pillow-95183
06/20/2022, 7:20 AMdamp-greece-33054
06/20/2022, 8:40 AMbrash-train-33431
06/20/2022, 11:05 PMnerdctl run -p 9200:9200 -p 9300:9300 -e "discovery.type=single-node" -v elast_data:/usr/share/elasticsearch/data elasticsearch:6.6.0
or nerdctl pull elasticsearch:6.6.0
on my macOS but i am getting the following error FATA[0001] no match for platform in manifest: not found
I believe it is something regarding the architecture definition that is not ARM or x64. I am not sure.
when I try to run the command with the flag --all-platforms
it works but it doesn't work for me nerdctl pull elasticsearch:6.6.0 --all-platforms
bland-ram-39507
06/21/2022, 10:15 AMsticky-summer-13450
06/21/2022, 11:54 AMdocker build ...
on the Linux command line and the image was built in RD.
I realised I got the tag name wrong, so I did a new docker build ...
with the correct -t
option and docker essentially just tagged the same Image ID with the new tag.
If I do an "Images -> Delete" in RD of the first image I get this error:
Error response from daemon: conflict: unable to delete bde8ceea4fa1 (must be forced) - image is referenced in multiple repositories
Yes, the same Image ID occurs twice, but I want to delete the wrongly tagged one. It is standard for one Image ID to be tagged with different tags, and standard to be able to delete tags.
I can, of cause, remove the image with docker image rm ...
so the RD interface should be able to do the same.ripe-traffic-25731
06/21/2022, 4:38 PMerror: failed to solve: failed to read dockerfile: open /tmp/buildkit-mount2585923853/Dockerfile: no such file or directory
Apparently nerdctl or the build process does not get the correct context defined in docker-compose.yml.chilly-lock-81867
06/22/2022, 5:41 AMsalmon-art-19742
06/22/2022, 4:35 PMshy-eye-35765
06/22/2022, 6:06 PMtime="2022-06-22T23:11:14+05:30" level=debug msg="interpreting argument \"0\" as an instance name"
time="2022-06-22T23:11:14+05:30" level=info msg="Using the existing instance \"0\""
time="2022-06-22T23:11:14+05:30" level=debug msg="Make sure \"rancher-desktop-bridged_en0\" network is running"
time="2022-06-22T23:11:14+05:30" level=fatal msg="networks.yaml field `paths.vdeSwitch` error: dir \"/opt\" is world-writable"
2022-06-22T17:41:14.020Z: + limactl --debug start --tty=false 0
2022-06-22T17:41:14.020Z: Error: /Applications/Rancher <http://Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl|Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl> exited with code 1
2022-06-22T17:41:14.021Z: Error starting lima: Error: /Applications/Rancher <http://Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl|Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl> exited with code 1
at ChildProcess.<anonymous> (/Applications/Rancher <http://Desktop.app/Contents/Resources/app.asar/dist/app/background.js:17:141990|Desktop.app/Contents/Resources/app.asar/dist/app/background.js:17:141990>)
at ChildProcess.emit (node:events:390:28)
at Process.ChildProcess._handle.onexit (node:internal/child_process:290:12) {
command: [
'/Applications/Rancher <http://Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl|Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl>',
'--debug',
'start',
'--tty=false',
'0'
]
}
==> background.log <==
2022-06-22T17:41:14.026Z: Kubernetes was unable to start: Error: /Applications/Rancher <http://Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl|Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl> exited with code 1
at ChildProcess.<anonymous> (/Applications/Rancher <http://Desktop.app/Contents/Resources/app.asar/dist/app/background.js:17:141990|Desktop.app/Contents/Resources/app.asar/dist/app/background.js:17:141990>)
at ChildProcess.emit (node:events:390:28)
at Process.ChildProcess._handle.onexit (node:internal/child_process:290:12) {
command: [
'/Applications/Rancher <http://Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl|Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl>',
'--debug',
'start',
'--tty=false',
'0'
]
}
I tried following https://github.com/rancher-sandbox/rancher-desktop/issues/1815. But in my case there was nothing at this path.
/private/var/run/rancher-desktop-lima
Hence I ran
sudo mkdir -m 775 /private/var/run/rancher-desktop-lima
But still getting same error.brave-grass-2915
06/23/2022, 8:46 AMnutritious-application-85076
06/23/2022, 2:31 PMnutritious-application-85076
06/23/2022, 2:33 PMapiVersion: v1
kind: Node
metadata:
annotations:
<http://alpha.kubernetes.io/provided-node-ip|alpha.kubernetes.io/provided-node-ip>: 192.168.205.2
Nevertheless this IP address do not correspond to the Lima VM Eth0 IP
lima-rancher-desktop:/Users/cmoullia$ ifconfig
eth0 Link encap:Ethernet HWaddr 52:55:55:4A:B8:EC
inet addr:192.168.5.15 Bcast:0.0.0.0 Mask:255.255.255.0
So I'm wondering where this IP is configured and if we can access it from the local machine (= macbook) ?average-iron-93428
06/23/2022, 2:56 PMnerdctl
works except it doesn't work with --platform amd64
and I get binary exec format errors.careful-piano-35019
06/23/2022, 10:12 PM$ kubectl get pods --namespace hub-agent
NAME READY STATUS RESTARTS AGE
traefik-hub-6977c67669-9x5lb 1/1 Running 0 19m
nothing outstanding in pod logs
the agent is identified in the hub but never completes its initnutritious-application-85076
06/24/2022, 8:43 AMlima and limactl
are used ?purple-fireman-44165
06/24/2022, 1:17 PMbulky-chef-93710
06/24/2022, 6:37 PMError: Client network socket disconnected before secure TLS connection was established
I was on version 1.0.0 so I tried upgrading to 1.4.1 (latest) but ultimately ran into the exact same error. This error occurs in a popup after a few minutes being the in the status of "Waiting for services" in the bottom left. This is on Windows 10 - x64 based processor also with Ubuntu WSL2 VM running.
Any help would be appreciateddazzling-carpenter-7851
06/27/2022, 6:40 AMnutritious-application-85076
06/27/2022, 10:52 AMthousands-insurance-91206
06/27/2022, 12:24 PMbest-pizza-1353
06/27/2022, 6:07 PMdb:
image: mongo
restart: always
volumes:
- ./data/db:/data/db
and get the following error in the container when trying to run it:
chown: changing ownership of '/data/db': Permission denied
stale-dinner-99388
06/28/2022, 8:29 AMroot@xxxx ~ # kubectl exec -ti rancher-865f7d9454-7s6dt -n cattle-system reset-password
kubectl exec [POD] [COMMAND] is DEPRECATED and will be removed in a future version. Use kubectl exec [POD] -- [COMMAND] instead.
W0628 02:05:50.193004 14484 client_config.go:617] Neither --kubeconfig nor --master was specified. Using the inClusterConfig. This might not work.
2 users were found with <http://authz.management.cattle.io/bootstrapping=admin-user|authz.management.cattle.io/bootstrapping=admin-user> label. They are [user-5wmpr user-nkh57]. Can only reset the default admin password when there is exactly one user with this label
command terminated with exit code 1
root@xxxx ~ # kubectl get user
NAME AGE
u-6kh6x 26d
u-b4qkhsnliz 26d
u-mo773yttt4 26d
user-5wmpr 26d
user-nkh57 3d8h
kubectl --kubeconfig $KUBECONFIG -n cattle-system exec $(kubectl --kubeconfig $KUBECONFIG -n cattle-system get pods -l app=rancher | grep '1/1' | head -1 | awk '{ print $1 }') -- ensure-default-admin
W0628 02:04:17.855783 14514 client_config.go:617] Neither --kubeconfig nor --master was specified. Using the inClusterConfig. This might not work.
Found existing default admin user (user-nkh57)
Existing default admin user (user-nkh57) is already enabled
Existing default admin user (user-nkh57) already labeled as admin
Existing default admin user (user-nkh57) is already an admin
billowy-bear-87489
06/28/2022, 1:44 PMaloof-motorcycle-79468
06/28/2022, 5:36 PMbrave-afternoon-4801
06/28/2022, 11:09 PMwhite-vegetable-30350
06/29/2022, 3:27 PM