text:
Fixes #15: Update default k3s version.

Closes #15.

LGTM

source: gharchive/pull-request

license_type: permissive

license_source: github-api


text:
Question: How registries.yaml can have multiple repositories

I have a single machine k3s installation for dev/test purposes.
The app images produced by our team are on GitLab.
I have the following registries.yaml:
mirrors:
  docker.io:
    endpoint:
      - "https://registry.gitlab.com"
configs:
  "registry.gitlab.com":
    auth:
      username: {{ username }}
      password: {{ gitlab_registry_token }}

It works fine to pull images from GitLab private registry, but it appears this registry is not working as a proxy for docker.io.
So, If I want to grab an image from docker.io (like nginx), I couldn't.
So my question how we can have multiple container repositories in registries.yaml

I tried to add an entry for "https://index.docker.io/v2/" in the endpoints list but It seems it is not working

Does the nginx image exist on gitlab at registry.gitlab.com/nginx:latest? If you want to use your registry as a mirror for docker.io, the images need to have the exact same name.

the image doesn't exist on registry.gitlab.com.
The Gitlab registry contains only my project images.
And I need to have Github for rancher and other images (nginx and others)

You've told it to use registry.gitlab.com as a mirror for docker.io. If that's not what you want, don'd do it. Did you mean to do something like this:
mirrors:
  registry.gitlab.com:
    endpoint:
      - "https://registry.gitlab.com"
configs:
  registry.gitlab.com:
    auth:
      username: {{ username }}
      password: {{ gitlab_registry_token }}

It seems working fine.  Thanks a lot.

source: gharchive/issue

authors: brandond mhewedy

license_source: bigquery


text:
Deleting node, reinstalling and rejoining fails with node password rejected

Steps to reproduce
Create 2 node cluster
Uninstall k3s-agent through uninstall script
delete node on master
install k3s-agent like before
result:
node joining is rejected because of invalid password
I probably need to delete this password somewhere, I however have no idea where.
Any insight in the matter would be greatly appreciated

found it, the password is stored in: /var/lib/rancher/k3s/server/node-passwd
removing the entry resolves the problem

I  had this same issue. The file I had to update was on the master node and was /var/lib/rancher/k3s/server/cred/node-passwd. Remove the line with the hostname that is causing issues then I rebooted that agent server.

authors: NickyHeuperman mrconnerton


text:
Update amis for new 1.13 (and 1.12, 1.11) k8s default

Update eks amis
Issue:
https://github.com/rancher/rancher/issues/21992

LGTM, AMIs and regions match the list from AMZ

lgtm

authors: dramich luthermonson rmweir

repo: rancher/kontainer-engine


text:
Capacity aware dynamic volume provisioning

HI,
Is there any plan to add "capacity aware volume scheduling" like the way topLVM does?
https://www.youtube.com/watch?v=ocERHX3uPtA
https://kccnceu20.sched.com/event/ZerD

No for now. But we can investigate it first.
Can you describe your use case? Thank you.

authors: derekbit rajivml

repo: rancher/local-path-provisioner


text:
Can't ssh into AWS "nano" instances

RancherOS Version: (ros os version)
ami-05d4ee63
Where are you running RancherOS? (docker-machine, AWS, GCE, baremetal, etc.)
AWS
Description
I thought I'd run RancherOS to run a single Web server container behind an auto-scaling group (very low traffic).
Given that RancherOS is a 50MB ISO, and the container I was planning to run is just a Go program taking up 5MB, I thought I'd be OK to run Nano instances and I could scale horizontally at peak times if required (probably not). Nano instances only cost $5 a month too.
I put together cloud-config to run the container, but the container never started up and my AWS SSH keys were rejected, asking for a password instead. When I upped the size to micro, no problems, the container started and I could SSH in.
So I guess it doesn't work at nano-scale which surprised me.
I'm not using Rancher at all for this so it's probably not related to https://github.com/rancher/os/issues/872
The docs in the AWS Marketplace "recommend" micro, but how about making it impossible to start the ami or getting the machines to shut themselves down since it doesn't work at nano?

I was looking into this the other day, and it turns out that the docker load of the system images we do at initial boot seems to fail when you use this size vm. I've got a change coming that will cause it to panic when that happens (as you get an undefined result), and then for 1.1 I might have a cunning plan - maybe :)

VM's that don't have enough memory should fail in obvious ways from 1.0.1-rc3 onwards due to #1788

and to show the log from a t3.nano with the logging change I made for v1.0.1-rc3 - docker load isn't made for saving memory, so in future we'll work to remove it (long term the plan is containerd)
[    7.526698] Freeing unused kernel memory: 1108K (ffff89495c6eb000 - ffff89495c800000)
[    7.531135] Freeing unused kernel memory: 384K (ffff89495cba0000 - ffff89495cc00000)
INFO[0000] Mounting state device /dev/xvda1 to /state
[    7.695447] EXT4-fs (xvda1): recovery complete
[    7.697361] EXT4-fs (xvda1): mounted filesystem with ordered data mode. Opts: (null)
INFO[0000] Waiting for Docker at unix:///var/run/system-docker.sock
[    7.740332] time="2017-04-25T04:06:43Z" level=debug msg="START: [/usr/bin/system-docker daemon --graph /var/lib/system-docker --userland-proxy=false --bridge none --group root --restart=false --storage-driver overlay --host unix:///var/run/system-docker.sock] in /"
INFO[0000] Connected to Docker at unix:///var/run/system-docker.sock
[    8.000098] tsc: Refined TSC clocksource calibration: 2399.998 MHz
[    8.002947] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x229835b7123, max_idle_ns: 440795242976 ns
INFO[0000] Loading images from /usr/share/ros/images.tar
FATA[0000] FATAL: failed loading images from /usr/share/ros/images.tar: Error response from daemon: Untar re-exec error: Non-zero exit code: 1: output: write /c5abd9d47d1220c3ccba42f9f7ad4c6fbb66b1dd3e87b2dd11be2549c56a1b3a/layer.tar: no space left on device
[    8.209427] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100
[    8.209427]
[    8.212273] CPU: 0 PID: 1 Comm: init Not tainted 4.9.24-rancher #1
[    8.212273] Hardware name: Xen HVM domU, BIOS 4.2.amazon 02/16/2017
[    8.212273]  ffff9ca7c000be20 ffffffff9a327906 ffff89495b280000 ffffffff9aa8d088
[    8.212273]  ffff9ca7c000bea0 ffffffff9a146207 ffff9ca700000010 ffff9ca7c000beb0
[    8.212273]  ffff9ca7c000be48 ffffffff9ac5eae8 0000000000000100 ffff89495b298010
[    8.212273] Call Trace:
[    8.212273]  [<ffffffff9a327906>] dump_stack+0x61/0x7d
[    8.212273]  [<ffffffff9a146207>] panic+0xd8/0x221
[    8.212273]  [<ffffffff9a06c67a>] do_exit+0x4d4/0x92c
[    8.212273]  [<ffffffff9a08b8f2>] ? wake_up_state+0x10/0x12
[    8.212273]  [<ffffffff9a074485>] ? signal_wake_up_state+0x2a/0x3b
[    8.212273]  [<ffffffff9a06cb49>] do_group_exit+0x41/0xa2
[    8.212273]  [<ffffffff9a06cbbe>] SyS_exit_group+0x14/0x14
[    8.212273]  [<ffffffff9a6e2e7b>] entry_SYSCALL_64_fastpath+0x1e/0xad
[    8.212273] Kernel Offset: 0x19000000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)

authors: SvenDowideit a-h

repo: rancher/os


text:
[UI] UI should prevent users to changed the per-host-subnet label

Rancher versions:
rancher/server: v1.6-development
rancher/net:v0.13.0
Docker version: (docker version,docker info preferred)
17.06.2-ce
Type/provider of hosts: (VirtualBox/Bare-metal/AWS/GCE/DO)
AWS
Environment Template: (Cattle/Kubernetes/Swarm/Mesos)
Cattle
When change/remove the per-hot-subnet label, Will produce a lot of routing rules on the host, will not be cleared.
link https://github.com/rancher/rancher/issues/10075

Rancher/server: 1.6.11-rc5     UI: 1.2.26
Rancher/server: 2.0.0-alpha10     UI: latest
Rancher 1.6 and Rancher 2.0 are test passed.

repo: rancher/rancher


text:
Rancher 2.x UI  edit or move namespace

Rancher version 2.1.1
There are two options in edit namespace.

Edit
Move

Using Move could move namespace from one project to other
Using Edit, select Default or System then save

It looks like move namespace to project Default

But refresh browser namespace still no belongs to a project

In Edit function, nothing you could change besides project. Why there is Edit function for namespace ?

In Edit function, nothing you could change besides project.

The description is editable., edit is confusing if it doesn't include the NS and Move exists because edit cannot be a bulk action.

UI sends the correct project Id to backend. But it looks like backend just ignored it.
I guess we should not allow user to update the project field in edit namespace modal.

@loganhz how is changing the project here different to the server than the move UI action?

oh yeah, that's new-ish.  Yes 2 API requests if the projectId has changed.

Version: master 2.2 (1/3/19)
Confirmed fix. I can use edit to both move a namespace and update it's description at the same time. When this happens we send a PUT to update the description and a POST to move the namespace. Once moved it now successfully moves even upon refresh. I also tested Move functionality without any issues. I could not reproduce the issue and HTTP/API looks good.


text:
Backport:Still see extra groups under Alerts some of the time

https://github.com/rancher/rancher/issues/19913

already in rc6

Version: v2.2.3-rc6
I can no longer reproduce the issue. I followed Logan's suggested steps (#19913 ) and also smoke tested for a while to try to reproduce the issue in other ways, such as waiting for a time, having various clusters with different alert rules/groups/etc. I still am not able to run into the issue so I believe this is safe to close. I will continue to keep an eye out to see if the issue happens again.

authors: davidnuzik loganhz


text:
Rancher 2.2.x Node Template AWS cloud provider kubelet proxy setting

What kind of request is this (question/bug/enhancement/feature request):
question/bug?
How to use node template in Rancher to set up kubelet proxy setting ?
Steps to reproduce (least amount of steps as possible):
AWS in proxy environment  (VPN set up with AWS Direct connect to company network)
Create node template with AWS provider
Engine Environment:

http_proxy: http://proxy:8080
https_proxy: http://proxy:8080
no_proxy:  localhost,127.0.0.1,169.254.169.254

AMI: RancherOS (rancheros-v1.5.1-hvm-1 - ami-0829d74b9ed70cb7a )
Update /etc/resolv.conf to correct nameservers
Create cluster in Rancher 2.2.x, add new node using node template
Result:
A new node provision in AWS, but Kubelet failed in Health check and go into crash loop
[workerPlane] Failed to bring up Worker Plane: [Failed to verify healthcheck: Failed to check https://localhost:10250/healthz for service [kubelet] on host [10.100.138.22]: Get https://localhost:10250/healthz: dial tcp [::1]:10250: connect: connection refused, log: I0618 03:53:17.586597 4417 aws.go:1007] Zone not specified in configuration file; querying AWS metadata service]
Other details that may be helpful:
No proxy setting for kubelet
docker inspect kubelet | grep proxy
Run curl inside kubelet container
curl -sSL https://ec2.ap-southeast-2.amazonaws.com/
Timeout
Login RancherOS
with proxy enabled
[rancher@middleware-rancher1 ~]$ wget -Y on https://ec2.ap-southeast-2.amazonaws.com/
Connecting to proxy:8080 (10.137.234.224:8080)
wget: tls error at line 803 cipher:0000
wget: error getting response: Connection reset by peer
proxy disable
[rancher@middleware-rancher1 ~]$ wget -Y off https://ec2.ap-southeast-2.amazonaws.com/
Connecting to ec2.ap-southeast-2.amazonaws.com (54.240.195.243:443)
wget: can't connect to remote host (54.240.195.243): Connection timed out
kubelet log
I0618 01:48:28.871807    6872 aws.go:1007] Zone not specified in configuration file; querying AWS metadata service
F0618 01:50:29.145579    6872 server.go:261] failed to run Kubelet: could not init cloud provider "aws": error finding instance i-0b7ceadcbb50f5ecf: "error listing AWS instances: "RequestError: send request failed\ncaused by: Post https://ec2.ap-southeast-2.amazonaws.com/: dial tcp 99.82.185.0:443: i/o timeout""
docker info
Containers: 9
Running: 7
Paused: 0
Stopped: 2
Images: 4
Server Version: 18.06.1-ce
Storage Driver: overlay
Backing Filesystem: extfs
Supports d_type: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: bridge host macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 468a545b9edcd5932818eb9de8e72413e616e86e
runc version: 2bb99b3d44a1de2769866941e698f93f540b910c (expected: 69663f0bd4b60df09991c08812a60108003fa340)
init version: fec3683
Security Options:
seccomp
Profile: default
Kernel Version: 4.14.85-rancher
Operating System: RancherOS v1.5.1
OSType: linux
Architecture: x86_64
CPUs: 1
Total Memory: 985.8MiB
Name: middleware-rancher1
ID: 5GO5:EFES:BS64:NXXS:EKTH:BIDQ:AOIW:D7UT:YNZZ:ZWWF:QZCI:CJFG
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
HTTP Proxy: http://proxy.auiag.corp:8080
HTTPS Proxy: http://proxy.auiag.corp:8080
No Proxy: localhost,127.0.0.1,169.254.169.254
Registry: https://index.docker.io/v1/
Labels:
provider=amazonec2
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false

See https://rancher.com/docs/rancher/v2.x/en/cluster-provisioning/rke-clusters/options/#config-file and https://rancher.com/docs/rke/latest/en/config-options/services/services-extras/#extra-environment-variables to set environment variables for k8s components. Let me know if that doesn't solve the issue.


text:
Taints - Cluster fails to come up when the nodes have taints with effect NoExecute

What kind of request is this (question/bug/enhancement/feature request): bug
Steps to reproduce (least amount of steps as possible):

Create a custom cluster. (Cluster spec: clusterrancher/rancher#1    - 1 etcd, 1 control plane and 1 worker node - with NoExecute taints on all of them, and clusterrancher/rancher#2    - 1 node - all roles - with taint)
Add taints on nodes while registering nodes.

Key: key1
Value: val1
Effect: NoExecute

Expected Result:
Cluster should deploy successfully with taints on the nodes.
Actual Result:
Error - [k8s] Job [rke-network-plugin-deploy-job] deletion timed out. Consider increasing addon_job_timeout value is seen on the UI and in the logs. The cluster is seen stuck in Provisioning state.
Note:

Even an rke cluster fails to come up when the nodes have NoExecute taints. Error - [k8s] Job [rke-network-plugin-deploy-job] deletion timed out. Consider increasing addon_job_timeout value
rke cluster spec - 1 node - All Roles

A custom cluster and an rke cluster with taints - NoSchedule works fine. Cluster comes up Active.

Other details that may be helpful:
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): master-head - latest
Installation option (single install/HA): single

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported): custom and rke
Kubernetes version (use kubectl version):

1.15.3

Docker version (use docker version):

18.9.8

We specified a node name in the add on job, so the job will be deployed to the exact the node we specified.
Even when the node has a NoSchedule taints which the job doesn’t tolerate. The job pod will be deployed to it. So this is the reason why NoSchedule works.  NoExecute will evict the pods on the node.
As we cannot deploy the addon jobs, cluster will not change to active state.

Verified on master-head commit id: d7b425da7
Steps:

Create an rke cluster. 1etcd, 1 control plane 1 worker
Add taints on nodes while registering nodes.

Key: key1
Value: val1
Effect: NoExecute

Cluster comes up successfully and is in Active state.
Also verified using custom cluster - 1etcd, 1 control plane 1 worker. Cluster comes up Active


text:
Rancher 2.5 (Single Install) not starting after nf_conntrack_max value adjustment

What kind of request is this (question/bug/enhancement/feature request): bug
Steps to reproduce (least amount of steps as possible):
In this scenario, the Docker Host where the Rancher container is started is a LXC container.
root@ubuntu4:~# sysctl -a|grep conntrack_max
net.netfilter.nf_conntrack_max = 524288

root@ubuntu4:~# docker run -d --name rancher --restart=unless-stopped -p 80:80 -p 443:443 --privileged rancher/rancher:v2.5.8

Installation and setup works fine.
Now the nf_conntrack_max value is set to another value on the LXC host:
root@host ~ # sysctl -w net.netfilter.nf_conntrack_max=525000
net.netfilter.nf_conntrack_max = 525000

Inside the LXC container, the nested Rancher container is restarted:
root@ubuntu4:~# docker restart rancher

root@ubuntu4:~# docker logs --follow rancher
[...]
I0624 07:38:23.051838      54 node.go:136] Successfully retrieved node IP: 172.17.0.2
I0624 07:38:23.051867      54 server_others.go:143] kube-proxy node IP is an IPv4 address (172.17.0.2), assume IPv4 operation
I0624 07:38:23.052887      54 server_others.go:186] Using iptables Proxier.
I0624 07:38:23.053288      54 server.go:650] Version: v1.19.8+k3s1
I0624 07:38:23.053960      54 conntrack.go:103] Set sysctl 'net/netfilter/nf_conntrack_max' to 524288
F0624 07:38:23.053999      54 server.go:495] open /proc/sys/net/netfilter/nf_conntrack_max: permission denied
2021/06/24 07:38:23 [FATAL] k3s exited with: exit status 1

Result:
Start of Rancher container fails. At least if the current value is same or higher than the remembered value.
Expected Result:
Start of Rancher container succeeds.
Other details that may be helpful:
The problem seems to be in the func realConntracker in k3s/conntrack.go:
https://github.com/k3s-io/k3s/blob/master/vendor/k8s.io/kubernetes/cmd/kube-proxy/app/conntrack.go#L98
This function checks the current sysctl value and compares it to a (somewhere internally retained?) internal value:
func (realConntracker) setIntSysCtl(name string, value int) error {
	entry := "net/netfilter/" + name

	sys := sysctl.New()
	if val, _ := sys.GetSysctl(entry); val != value {
		klog.Infof("Set sysctl '%v' to %v", entry, value)
		if err := sys.SetSysctl(entry, value); err != nil {
			return err
		}
	}
	return nil
}

If the current system value doesn't match the internal value, sys.SetSysctl is launched to set the previously known value. Yet this fails in a LXC container as the value is defined at Host level:
root@ubuntu4:~# sysctl -w net/netfilter/nf_conntrack_max=524288
root@ubuntu4:~# sysctl -a|grep conntrack_max
net.netfilter.nf_conntrack_max = 525000

Probably related: https://github.com/kubernetes-sigs/kind/pull/2241
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): 2.5.8

Installation option (single install/HA): Single Install

Docker version (use docker version):

root@ubuntu4:~# docker version
Client:
 Version:           20.10.2
 API version:       1.41
 Go version:        go1.13.8
 Git commit:        20.10.2-0ubuntu1~20.04.2
 Built:             Tue Mar 30 21:24:57 2021
 OS/Arch:           linux/amd64
 Context:           default
 Experimental:      true

Server:
 Engine:
  Version:          20.10.2
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.13.8
  Git commit:       20.10.2-0ubuntu1~20.04.2
  Built:            Mon Mar 29 19:10:09 2021
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.4.4-0ubuntu1~20.04.2
  GitCommit:
 runc:
  Version:          1.0.0~rc95-0ubuntu1~20.04.1
  GitCommit:
 docker-init:
  Version:          0.19.0
  GitCommit:

This issue appears to be dependent on upstream: https://github.com/k3s-io/k3s/pull/3505#issuecomment-867795852

This also affects/breaks deploying a Rancher managed Kubernetes cluster to nodes. The Kubernetes deployment is stuck on kube-proxy deployment. kube-proxy tries to set a specific value as nf_conntrack_max but fails:
I0723 07:30:08.943595   12314 node.go:172] Successfully retrieved node IP: 172.17.0.1
I0723 07:30:08.943627   12314 server_others.go:142] kube-proxy node IP is an IPv4 address (172.17.0.1), assume IPv4 operation
W0723 07:30:08.944553   12314 server_others.go:584] Unknown proxy mode "", assuming iptables proxy
I0723 07:30:08.944629   12314 server_others.go:182] DetectLocalMode: 'ClusterCIDR'
I0723 07:30:08.944652   12314 server_others.go:185] Using iptables Proxier.
I0723 07:30:08.944760   12314 proxier.go:287] iptables(IPv4) masquerade mark: 0x00004000
I0723 07:30:08.944857   12314 proxier.go:334] iptables(IPv4) sync params: minSyncPeriod=1s, syncPeriod=30s, burstSyncs=2
I0723 07:30:08.944977   12314 proxier.go:346] iptables(IPv4) supports --random-fully
I0723 07:30:08.945162   12314 server.go:650] Version: v1.20.8
I0723 07:30:08.945589   12314 conntrack.go:100] Set sysctl 'net/netfilter/nf_conntrack_max' to 131072
F0723 07:30:08.945634   12314 server.go:495] open /proc/sys/net/netfilter/nf_conntrack_max: permission denied

kube-proxy is then restarted in a loop, trying to fix it.
On Rancher server side, the following error is logged:
2021/07/23 07:40:55 [ERROR] Failed to upgrade worker components on NotReady hosts, error: [Failed to verify healthcheck: Failed to check http://localhost:10256/healthz for service [kube-proxy] on host [192.168.15.161]: Get "http://localhost:10256/healthz": dial tcp 127.0.0.1:10256: connect: connection refused, log: F0723 07:40:32.920751   19619 server.go:495] open /proc/sys/net/netfilter/nf_conntrack_max: permission denied]

This breaks Rancher Kubernetes deployments in LXC and LXD environments.
My Kubernetes PR is still open unfortunately.

On master-head - commit id: 94bca993f
docker install rancher works and rancher server comes up.

@sowmyav27 Did you try this inside a container? Now change the value of nf_conntrack_max on the host. Then restart Rancher. What happens? Please don't just close issues without proper validation, thanks.
Also, this does not only apply to the Single Rancher Install (as mentioned in https://github.com/rancher/rancher/issues/33360#issuecomment-885462965) but also to deployments of new Kubernetes clusters from within Rancher (Rancher deployed Kubernetes clusters).

@Napsty It has been fixed in k3s version: v1.21.3+k3s1 Related PR - https://github.com/k3s-io/k3s/pull/3341 and this version is embedded in the rancher version that was tested on .

@sowmyav27 Alright, I was missing that information then, thanks for sharing the PR.
That covers the k3s part but not the k8s from Rancher launched clusters. How will this be solved?

Hi @Napsty - the issue was originally filed for single node install, as mentioned in the title, so that's why we validated for it in particular.
However, I do see your recent comment (https://github.com/rancher/rancher/issues/33360#issuecomment-885462965), so we should validate that as well.

not the k8s from Rancher launched clusters
How are you launching these clusters? Is there a reproducible workflow? I presume this is with RKE.

Yes, the title of the issue is a bit misleading. I only got aware that the same issue also affects k8s installations later.
To reproduce you can basically just create a new Kubernetes cluster from within the Rancher interface (create new cluster, custom). Just make sure the cluster nodes are actually containers. I was able to reproduce with LXC and LXD containers. I am not 100% certain but I believe this method uses rke launched from Rancher itself.
As mentioned in the previous comments, a workaround is to change kube-proxy conntrack to ignore higher values. With this workaround the Kubernetes deployment should not get stuck at kube-proxy deployment anymore as long as the hosts value is high enough (which can be prepared in advance). As conntrack comes from Kubernetes upstream, it probably needs to be fixed there but my PR there seems to attract nobody 😅
Thanks for looking into this.

Just make sure the cluster nodes are actually containers

Rancher 2.5 creates downstream clusters with RKE when you select "custom". When you are given the Docker run command, it sets up a node for an RKE cluster. I believe you may be encountering an unsupported use case
From the RKE docs: "It works on bare-metal and virtualized servers."

https://rancher.com/docs/rancher/v2.5/en/cluster-provisioning/node-requirements/
https://rancher.com/docs/rke/latest/en/

Does this fail when you create cluster nodes that aren't containers?

Does this fail when you create cluster nodes that aren't containers?

No, it works fine in VMs and bare-metal.
Thanks for the edit part ;-). Yes, it would mean a large improvement. Rancher managed clusters could be rolled out much quicker (in LXC/LXD environments). Thx for fixing it in k3s with a workaround. I guess to work in k8s (rke deployed Kubernetes) this needs to be fixed in k8s upstream (see my PR).
We can leave this ticket closed or if you prefer I change the issue subject.

Actually I have to revise my last comment.
I just wanted to install a clean new install of Rancher 2.5.9 Single Node Install inside a KVM. Installation of Rancher fails.
Environment: Virtual Machine (KVM), Ubuntu 20.04 (guest OS), 4vCPU, 8GB Memory
2021/08/03 10:47:49 [INFO] Rancher version v2.5.9 (3c5418944) is starting
2021/08/03 10:47:49 [INFO] Rancher arguments {ACMEDomains:[] AddLocal:true Embedded:false BindHost: HTTPListenPort:80 HTTPSListenPort:443 K8sMode:auto Debug:false Trace:false NoCACerts:false AuditLogPath:/var/log/auditlog/rancher-api-audit.log AuditLogMaxage:10 AuditLogMaxsize:100 AuditLogMaxbackup:10 AuditLevel:0 Agent:false Features: ClusterRegistry:}
2021/08/03 10:47:49 [INFO] Listening on /tmp/log.sock
2021/08/03 10:47:49 [INFO] Running etcd --data-dir=management-state/etcd --heartbeat-interval=500 --election-timeout=5000
2021-08-03 10:47:49.106840 W | pkg/flags: unrecognized environment variable ETCD_URL_arm64=https://github.com/etcd-io/etcd/releases/download/v3.4.3/etcd-v3.4.3-linux-arm64.tar.gz
2021-08-03 10:47:49.106904 W | pkg/flags: unrecognized environment variable ETCD_URL_amd64=https://github.com/etcd-io/etcd/releases/download/v3.4.3/etcd-v3.4.3-linux-amd64.tar.gz
2021-08-03 10:47:49.106914 W | pkg/flags: unrecognized environment variable ETCD_UNSUPPORTED_ARCH=amd64
2021-08-03 10:47:49.106927 W | pkg/flags: unrecognized environment variable ETCD_URL=ETCD_URL_amd64
[WARNING] Deprecated '--logger=capnslog' flag is set; use '--logger=zap' flag instead
2021-08-03 10:47:49.106982 I | etcdmain: etcd Version: 3.4.3
2021-08-03 10:47:49.106995 I | etcdmain: Git SHA: 3cf2f69b5
2021-08-03 10:47:49.107001 I | etcdmain: Go Version: go1.12.12
2021-08-03 10:47:49.107012 I | etcdmain: Go OS/Arch: linux/amd64
2021-08-03 10:47:49.107024 I | etcdmain: setting maximum number of CPUs to 4, total number of available CPUs is 4
2021-08-03 10:47:49.107141 N | etcdmain: the server is already initialized as member before, starting as etcd member...
[WARNING] Deprecated '--logger=capnslog' flag is set; use '--logger=zap' flag instead
2021-08-03 10:47:49.107849 I | embed: name = default
2021-08-03 10:47:49.107880 I | embed: data dir = management-state/etcd
2021-08-03 10:47:49.107888 I | embed: member dir = management-state/etcd/member
2021-08-03 10:47:49.107895 I | embed: heartbeat = 500ms
2021-08-03 10:47:49.107902 I | embed: election = 5000ms
2021-08-03 10:47:49.107915 I | embed: snapshot count = 100000
2021-08-03 10:47:49.107977 I | embed: advertise client URLs = http://localhost:2379
2021-08-03 10:47:49.107995 I | embed: initial advertise peer URLs = http://localhost:2380
2021-08-03 10:47:49.108009 I | embed: initial cluster =
2021-08-03 10:47:49.114885 I | etcdserver: restarting member 8e9e05c52164694d in cluster cdf818194e3a8c32 at commit index 577
raft2021/08/03 10:47:49 INFO: 8e9e05c52164694d switched to configuration voters=()
raft2021/08/03 10:47:49 INFO: 8e9e05c52164694d became follower at term 3
raft2021/08/03 10:47:49 INFO: newRaft 8e9e05c52164694d [peers: [], term: 3, commit: 577, applied: 0, lastindex: 577, lastterm: 3]
2021-08-03 10:47:49.122161 W | auth: simple token is not cryptographically signed
2021-08-03 10:47:49.124712 I | etcdserver: starting server... [version: 3.4.3, cluster version: to_be_decided]
raft2021/08/03 10:47:49 INFO: 8e9e05c52164694d switched to configuration voters=(10276657743932975437)
2021-08-03 10:47:49.126010 I | etcdserver/membership: added member 8e9e05c52164694d [http://localhost:2380] to cluster cdf818194e3a8c32
2021-08-03 10:47:49.126184 N | etcdserver/membership: set the initial cluster version to 3.4
2021-08-03 10:47:49.126290 I | etcdserver/api: enabled capabilities for version 3.4
2021-08-03 10:47:49.126844 I | embed: listening for peers on 127.0.0.1:2380
raft2021/08/03 10:47:55 INFO: 8e9e05c52164694d is starting a new election at term 3
raft2021/08/03 10:47:55 INFO: 8e9e05c52164694d became candidate at term 4
raft2021/08/03 10:47:55 INFO: 8e9e05c52164694d received MsgVoteResp from 8e9e05c52164694d at term 4
raft2021/08/03 10:47:55 INFO: 8e9e05c52164694d became leader at term 4
raft2021/08/03 10:47:55 INFO: raft.node: 8e9e05c52164694d elected leader 8e9e05c52164694d at term 4
2021-08-03 10:47:55.116855 I | etcdserver: published {Name:default ClientURLs:[http://localhost:2379]} to cluster cdf818194e3a8c32
2021-08-03 10:47:55.117072 I | embed: ready to serve client requests
2021-08-03 10:47:55.119245 N | embed: serving insecure client requests on 127.0.0.1:2379, this is strongly discouraged!
2021/08/03 10:47:55 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6443/version?timeout=15m0s": dial tcp 127.0.0.1:6443: connect: connection refused
time="2021-08-03T10:47:55.404406940Z" level=info msg="Starting k3s v1.19.8+k3s1 (95fc76b2)"
time="2021-08-03T10:47:55.404989488Z" level=info msg="Cluster bootstrap already complete"
time="2021-08-03T10:47:55.435299095Z" level=info msg="Running kube-apiserver --advertise-port=6443 --allow-privileged=true --anonymous-auth=false --api-audiences=unknown --authorization-mode=Node,RBAC --bind-address=127.0.0.1 --cert-dir=/var/lib/rancher/k3s/server/tls/temporary-certs --client-ca-file=/var/lib/rancher/k3s/server/tls/client-ca.crt --enable-admission-plugins=NodeRestriction --etcd-servers=http://localhost:2379 --insecure-port=0 --kubelet-certificate-authority=/var/lib/rancher/k3s/server/tls/server-ca.crt --kubelet-client-certificate=/var/lib/rancher/k3s/server/tls/client-kube-apiserver.crt --kubelet-client-key=/var/lib/rancher/k3s/server/tls/client-kube-apiserver.key --profiling=false --proxy-client-cert-file=/var/lib/rancher/k3s/server/tls/client-auth-proxy.crt --proxy-client-key-file=/var/lib/rancher/k3s/server/tls/client-auth-proxy.key --requestheader-allowed-names=system:auth-proxy --requestheader-client-ca-file=/var/lib/rancher/k3s/server/tls/request-header-ca.crt --requestheader-extra-headers-prefix=X-Remote-Extra- --requestheader-group-headers=X-Remote-Group --requestheader-username-headers=X-Remote-User --secure-port=6444 --service-account-issuer=k3s --service-account-key-file=/var/lib/rancher/k3s/server/tls/service.key --service-account-signing-key-file=/var/lib/rancher/k3s/server/tls/service.key --service-cluster-ip-range=10.43.0.0/16 --storage-backend=etcd3 --tls-cert-file=/var/lib/rancher/k3s/server/tls/serving-kube-apiserver.crt --tls-private-key-file=/var/lib/rancher/k3s/server/tls/serving-kube-apiserver.key"
I0803 10:47:55.438166      34 server.go:652] external host was not specified, using 172.17.0.2
I0803 10:47:55.439186      34 server.go:177] Version: v1.19.8+k3s1
I0803 10:47:55.460009      34 plugins.go:158] Loaded 12 mutating admission controller(s) successfully in the following order: NamespaceLifecycle,LimitRanger,ServiceAccount,NodeRestriction,TaintNodesByCondition,Priority,DefaultTolerationSeconds,DefaultStorageClass,StorageObjectInUseProtection,RuntimeClass,DefaultIngressClass,MutatingAdmissionWebhook.
I0803 10:47:55.460074      34 plugins.go:161] Loaded 10 validating admission controller(s) successfully in the following order: LimitRanger,ServiceAccount,Priority,PersistentVolumeClaimResize,RuntimeClass,CertificateApproval,CertificateSigning,CertificateSubjectRestriction,ValidatingAdmissionWebhook,ResourceQuota.
I0803 10:47:55.463217      34 plugins.go:158] Loaded 12 mutating admission controller(s) successfully in the following order: NamespaceLifecycle,LimitRanger,ServiceAccount,NodeRestriction,TaintNodesByCondition,Priority,DefaultTolerationSeconds,DefaultStorageClass,StorageObjectInUseProtection,RuntimeClass,DefaultIngressClass,MutatingAdmissionWebhook.
I0803 10:47:55.463254      34 plugins.go:161] Loaded 10 validating admission controller(s) successfully in the following order: LimitRanger,ServiceAccount,Priority,PersistentVolumeClaimResize,RuntimeClass,CertificateApproval,CertificateSigning,CertificateSubjectRestriction,ValidatingAdmissionWebhook,ResourceQuota.
I0803 10:47:55.516041      34 master.go:271] Using reconciler: lease
W0803 10:47:55.926248      34 genericapiserver.go:412] Skipping API batch/v2alpha1 because it has no resources.
W0803 10:47:55.945512      34 genericapiserver.go:412] Skipping API discovery.k8s.io/v1alpha1 because it has no resources.
W0803 10:47:55.981580      34 genericapiserver.go:412] Skipping API node.k8s.io/v1alpha1 because it has no resources.
W0803 10:47:56.045832      34 genericapiserver.go:412] Skipping API rbac.authorization.k8s.io/v1alpha1 because it has no resources.
W0803 10:47:56.049188      34 genericapiserver.go:412] Skipping API scheduling.k8s.io/v1alpha1 because it has no resources.
W0803 10:47:56.068143      34 genericapiserver.go:412] Skipping API storage.k8s.io/v1alpha1 because it has no resources.
W0803 10:47:56.091699      34 genericapiserver.go:412] Skipping API apps/v1beta2 because it has no resources.
W0803 10:47:56.091734      34 genericapiserver.go:412] Skipping API apps/v1beta1 because it has no resources.
I0803 10:47:56.102792      34 plugins.go:158] Loaded 12 mutating admission controller(s) successfully in the following order: NamespaceLifecycle,LimitRanger,ServiceAccount,NodeRestriction,TaintNodesByCondition,Priority,DefaultTolerationSeconds,DefaultStorageClass,StorageObjectInUseProtection,RuntimeClass,DefaultIngressClass,MutatingAdmissionWebhook.
I0803 10:47:56.102831      34 plugins.go:161] Loaded 10 validating admission controller(s) successfully in the following order: LimitRanger,ServiceAccount,Priority,PersistentVolumeClaimResize,RuntimeClass,CertificateApproval,CertificateSigning,CertificateSubjectRestriction,ValidatingAdmissionWebhook,ResourceQuota.
time="2021-08-03T10:47:56.117486702Z" level=info msg="Running kube-scheduler --address=127.0.0.1 --bind-address=127.0.0.1 --kubeconfig=/var/lib/rancher/k3s/server/cred/scheduler.kubeconfig --port=10251 --profiling=false --secure-port=0"
time="2021-08-03T10:47:56.117526487Z" level=info msg="Waiting for API server to become available"
I0803 10:47:56.117996      34 registry.go:173] Registering SelectorSpread plugin
I0803 10:47:56.118024      34 registry.go:173] Registering SelectorSpread plugin
time="2021-08-03T10:47:56.118586884Z" level=info msg="Running kube-controller-manager --address=127.0.0.1 --allocate-node-cidrs=true --bind-address=127.0.0.1 --cluster-cidr=10.42.0.0/16 --cluster-signing-cert-file=/var/lib/rancher/k3s/server/tls/client-ca.crt --cluster-signing-key-file=/var/lib/rancher/k3s/server/tls/client-ca.key --kubeconfig=/var/lib/rancher/k3s/server/cred/controller.kubeconfig --port=10252 --profiling=false --root-ca-file=/var/lib/rancher/k3s/server/tls/server-ca.crt --secure-port=0 --service-account-private-key-file=/var/lib/rancher/k3s/server/tls/service.key --use-service-account-credentials=true"
time="2021-08-03T10:47:56.121603426Z" level=info msg="Node token is available at /var/lib/rancher/k3s/server/token"
time="2021-08-03T10:47:56.121676173Z" level=info msg="To join node to cluster: k3s agent -s https://172.17.0.2:6443 -t ${NODE_TOKEN}"
time="2021-08-03T10:47:56.125076618Z" level=info msg="Wrote kubeconfig /etc/rancher/k3s/k3s.yaml"
time="2021-08-03T10:47:56.125163251Z" level=info msg="Run: k3s kubectl"
time="2021-08-03T10:47:56.125534450Z" level=info msg="Module overlay was already loaded"
time="2021-08-03T10:47:56.125590165Z" level=info msg="Module nf_conntrack was already loaded"
time="2021-08-03T10:47:56.125623247Z" level=info msg="Module br_netfilter was already loaded"
time="2021-08-03T10:47:56.125662752Z" level=info msg="Module iptable_nat was already loaded"
time="2021-08-03T10:47:56.150691402Z" level=info msg="Cluster-Http-Server 2021/08/03 10:47:56 http: TLS handshake error from 127.0.0.1:55380: remote error: tls: bad certificate"
time="2021-08-03T10:47:56.159468634Z" level=info msg="Cluster-Http-Server 2021/08/03 10:47:56 http: TLS handshake error from 127.0.0.1:55386: remote error: tls: bad certificate"
time="2021-08-03T10:47:56.182242979Z" level=info msg="certificate CN=local-node signed by CN=k3s-server-ca@1627987647: notBefore=2021-08-03 10:47:27 +0000 UTC notAfter=2022-08-03 10:47:56 +0000 UTC"
time="2021-08-03T10:47:56.189805213Z" level=info msg="certificate CN=system:node:local-node,O=system:nodes signed by CN=k3s-client-ca@1627987647: notBefore=2021-08-03 10:47:27 +0000 UTC notAfter=2022-08-03 10:47:56 +0000 UTC"
time="2021-08-03T10:47:56.202788256Z" level=info msg="Logging containerd to /var/lib/rancher/k3s/agent/containerd/containerd.log"
time="2021-08-03T10:47:56.203314847Z" level=info msg="Running containerd -c /var/lib/rancher/k3s/agent/etc/containerd/config.toml -a /run/k3s/containerd/containerd.sock --state /run/k3s/containerd --root /var/lib/rancher/k3s/agent/containerd"
W0803 10:47:57.183700      11 warnings.go:80] apiextensions.k8s.io/v1beta1 CustomResourceDefinition is deprecated in v1.16+, unavailable in v1.22+; use apiextensions.k8s.io/v1 CustomResourceDefinition
time="2021-08-03T10:47:57.205871940Z" level=info msg="Containerd is now running"
time="2021-08-03T10:47:57.218505485Z" level=info msg="Connecting to proxy" url="wss://127.0.0.1:6443/v1-k3s/connect"
time="2021-08-03T10:47:57.230260755Z" level=info msg="Handling backend connection request [local-node]"
time="2021-08-03T10:47:57.230981283Z" level=warning msg="Disabling CPU quotas due to missing cpu.cfs_period_us"
time="2021-08-03T10:47:57.231143909Z" level=info msg="Running kubelet --address=0.0.0.0 --anonymous-auth=false --authentication-token-webhook=true --authorization-mode=Webhook --cgroup-driver=cgroupfs --client-ca-file=/var/lib/rancher/k3s/agent/client-ca.crt --cloud-provider=external --cluster-dns=10.43.0.10 --cluster-domain=cluster.local --cni-bin-dir=/var/lib/rancher/k3s/data/ab1b521f47b3cbc273e0c667521084cff1ea3540d55b425ac7ed30c27daf92f8/bin --cni-conf-dir=/var/lib/rancher/k3s/agent/etc/cni/net.d --container-runtime-endpoint=/run/k3s/containerd/containerd.sock --container-runtime=remote --containerd=/run/k3s/containerd/containerd.sock --cpu-cfs-quota=false --eviction-hard=imagefs.available<5%,nodefs.available<5% --eviction-minimum-reclaim=imagefs.available=10%,nodefs.available=10% --fail-swap-on=false --healthz-bind-address=127.0.0.1 --hostname-override=local-node --kubeconfig=/var/lib/rancher/k3s/agent/kubelet.kubeconfig --kubelet-cgroups=/k3s --node-labels= --pod-manifest-path=/var/lib/rancher/k3s/agent/pod-manifests --read-only-port=0 --resolv-conf=/etc/resolv.conf --runtime-cgroups=/k3s --serialize-image-pulls=false --tls-cert-file=/var/lib/rancher/k3s/agent/serving-kubelet.crt --tls-private-key-file=/var/lib/rancher/k3s/agent/serving-kubelet.key"
time="2021-08-03T10:47:57.232737862Z" level=info msg="Running kube-proxy --cluster-cidr=10.42.0.0/16 --healthz-bind-address=127.0.0.1 --hostname-override=local-node --kubeconfig=/var/lib/rancher/k3s/agent/kubeproxy.kubeconfig --proxy-mode=iptables"
Flag --cloud-provider has been deprecated, will be removed in 1.23, in favor of removing cloud provider code from Kubelet.
Flag --containerd has been deprecated, This is a cadvisor flag that was mistakenly registered with the Kubelet. Due to legacy concerns, it will follow the standard CLI deprecation timeline before being removed.
I0803 10:47:57.238111      34 server.go:407] Version: v1.19.8+k3s1
W0803 10:47:57.239400      34 server.go:226] WARNING: all flags other than --config, --write-config-to, and --cleanup are deprecated. Please begin using a config file ASAP.
W0803 10:47:57.240983      11 warnings.go:80] apiextensions.k8s.io/v1beta1 CustomResourceDefinition is deprecated in v1.16+, unavailable in v1.22+; use apiextensions.k8s.io/v1 CustomResourceDefinition
W0803 10:47:57.244216      34 proxier.go:639] Failed to read file /lib/modules/5.4.0-80-generic/modules.builtin with error open /lib/modules/5.4.0-80-generic/modules.builtin: no such file or directory. You can ignore this message when kube-proxy is running inside container without mounting /lib/modules
W0803 10:47:57.245847      34 proxier.go:649] Failed to load kernel module ip_vs with modprobe. You can ignore this message when kube-proxy is running inside container without mounting /lib/modules
W0803 10:47:57.247811      34 proxier.go:649] Failed to load kernel module ip_vs_rr with modprobe. You can ignore this message when kube-proxy is running inside container without mounting /lib/modules
W0803 10:47:57.250566      34 proxier.go:649] Failed to load kernel module ip_vs_wrr with modprobe. You can ignore this message when kube-proxy is running inside container without mounting /lib/modules
W0803 10:47:57.253242      34 proxier.go:649] Failed to load kernel module ip_vs_sh with modprobe. You can ignore this message when kube-proxy is running inside container without mounting /lib/modules
W0803 10:47:57.255003      34 proxier.go:649] Failed to load kernel module nf_conntrack with modprobe. You can ignore this message when kube-proxy is running inside container without mounting /lib/modules
time="2021-08-03T10:47:57.275604610Z" level=info msg="Waiting for node local-node CIDR not assigned yet"
E0803 10:47:57.290613      34 node.go:125] Failed to retrieve node info: nodes "local-node" is forbidden: User "system:kube-proxy" cannot get resource "nodes" in API group "" at the cluster scope
W0803 10:47:57.300698      11 warnings.go:80] apiextensions.k8s.io/v1beta1 CustomResourceDefinition is deprecated in v1.16+, unavailable in v1.22+; use apiextensions.k8s.io/v1 CustomResourceDefinition
I0803 10:47:57.311211      34 dynamic_cafile_content.go:167] Starting client-ca-bundle::/var/lib/rancher/k3s/agent/client-ca.crt
I0803 10:47:58.368243      34 dynamic_cafile_content.go:167] Starting request-header::/var/lib/rancher/k3s/server/tls/request-header-ca.crt
I0803 10:47:58.368488      34 dynamic_cafile_content.go:167] Starting client-ca-bundle::/var/lib/rancher/k3s/server/tls/client-ca.crt
I0803 10:47:58.368657      34 dynamic_serving_content.go:130] Starting serving-cert::/var/lib/rancher/k3s/server/tls/serving-kube-apiserver.crt::/var/lib/rancher/k3s/server/tls/serving-kube-apiserver.key
I0803 10:47:58.369515      34 secure_serving.go:197] Serving securely on 127.0.0.1:6444
I0803 10:47:58.369583      34 apiservice_controller.go:97] Starting APIServiceRegistrationController
I0803 10:47:58.369593      34 cache.go:32] Waiting for caches to sync for APIServiceRegistrationController controller
I0803 10:47:58.369612      34 tlsconfig.go:240] Starting DynamicServingCertificateController
I0803 10:47:58.370321      34 available_controller.go:475] Starting AvailableConditionController
I0803 10:47:58.370332      34 cache.go:32] Waiting for caches to sync for AvailableConditionController controller
I0803 10:47:58.370367      34 autoregister_controller.go:141] Starting autoregister controller
I0803 10:47:58.370371      34 cache.go:32] Waiting for caches to sync for autoregister controller
I0803 10:47:58.371163      34 cluster_authentication_trust_controller.go:440] Starting cluster_authentication_trust_controller controller
I0803 10:47:58.371174      34 shared_informer.go:240] Waiting for caches to sync for cluster_authentication_trust_controller
I0803 10:47:58.371256      34 controller.go:83] Starting OpenAPI AggregationController
I0803 10:47:58.371648      34 customresource_discovery_controller.go:209] Starting DiscoveryController
I0803 10:47:58.371959      34 crdregistration_controller.go:111] Starting crd-autoregister controller
I0803 10:47:58.371968      34 shared_informer.go:240] Waiting for caches to sync for crd-autoregister
I0803 10:47:58.371995      34 dynamic_cafile_content.go:167] Starting client-ca-bundle::/var/lib/rancher/k3s/server/tls/client-ca.crt
I0803 10:47:58.372108      34 dynamic_cafile_content.go:167] Starting request-header::/var/lib/rancher/k3s/server/tls/request-header-ca.crt
I0803 10:47:58.372987      34 dynamic_serving_content.go:130] Starting aggregator-proxy-cert::/var/lib/rancher/k3s/server/tls/client-auth-proxy.crt::/var/lib/rancher/k3s/server/tls/client-auth-proxy.key
I0803 10:47:58.374442      34 controller.go:86] Starting OpenAPI controller
I0803 10:47:58.374841      34 naming_controller.go:291] Starting NamingConditionController
I0803 10:47:58.375297      34 establishing_controller.go:76] Starting EstablishingController
I0803 10:47:58.375748      34 nonstructuralschema_controller.go:186] Starting NonStructuralSchemaConditionController
I0803 10:47:58.376140      34 apiapproval_controller.go:186] Starting KubernetesAPIApprovalPolicyConformantConditionController
I0803 10:47:58.376542      34 crd_finalizer.go:266] Starting CRDFinalizer
time="2021-08-03T10:47:58.419755275Z" level=info msg="Running cloud-controller-manager --allocate-node-cidrs=true --allow-untagged-cloud=true --bind-address=127.0.0.1 --cloud-provider=k3s --cluster-cidr=10.42.0.0/16 --kubeconfig=/var/lib/rancher/k3s/server/cred/cloud-controller.kubeconfig --node-status-update-frequency=1m --profiling=false --secure-port=0"
Flag --allow-untagged-cloud has been deprecated, This flag is deprecated and will be removed in a future release. A cluster-id will be required on cloud instances.
I0803 10:47:58.423592      34 controllermanager.go:127] Version: v1.19.8+k3s1
W0803 10:47:58.423633      34 controllermanager.go:139] detected a cluster without a ClusterID.  A ClusterID will be required in the future.  Please tag your cluster to avoid any future issues
I0803 10:47:58.423731      34 leaderelection.go:243] attempting to acquire leader lease  kube-system/cloud-controller-manager...
E0803 10:47:58.426840      34 leaderelection.go:325] error retrieving resource lock kube-system/cloud-controller-manager: endpoints "cloud-controller-manager" is forbidden: User "cloud-controller-manager" cannot get resource "endpoints" in API group "" in the namespace "kube-system": RBAC: [clusterrole.rbac.authorization.k8s.io "cloud-controller-manager" not found, clusterrole.rbac.authorization.k8s.io "system:public-info-viewer" not found, clusterrole.rbac.authorization.k8s.io "system:basic-user" not found, clusterrole.rbac.authorization.k8s.io "system:discovery" not found]
E0803 10:47:58.439901      34 controller.go:156] Unable to remove old endpoints from kubernetes service: no master IPs were listed in storage, refusing to erase all endpoints for the kubernetes service
I0803 10:47:58.449587      34 node.go:136] Successfully retrieved node IP: 172.17.0.2
I0803 10:47:58.449615      34 server_others.go:143] kube-proxy node IP is an IPv4 address (172.17.0.2), assume IPv4 operation
I0803 10:47:58.450447      34 server_others.go:186] Using iptables Proxier.
I0803 10:47:58.450606      34 server.go:650] Version: v1.19.8+k3s1
I0803 10:47:58.450909      34 conntrack.go:103] Set sysctl 'net/netfilter/nf_conntrack_max' to 131072
F0803 10:47:58.450942      34 server.go:495] open /proc/sys/net/netfilter/nf_conntrack_max: permission denied
2021/08/03 10:47:58 [FATAL] k3s exited with: exit status 1

Inside the KVM itself I am able to change the nf_conntrack_max value:
root@pgk8s:~# sysctl net/netfilter/nf_conntrack_max
net.netfilter.nf_conntrack_max = 262144

root@pgk8s:~# sysctl -w net/netfilter/nf_conntrack_max=131072
net.netfilter.nf_conntrack_max = 131072

root@pgk8s:~# sysctl net/netfilter/nf_conntrack_max
net.netfilter.nf_conntrack_max = 131072

The fact that a container (rancher) wants to change nf_conntrack_max interferes with the Linux Kernel's non net-init policy - hence permission denied. So the bug report actually also affects installations other than inside LXC/LXD environments.
@sowmyav27 You mentioned this:

It has been fixed in k3s version: v1.21.3+k3s1 Related PR - k3s-io/k3s#3341 and this version is embedded in the rancher version that was tested on .

Which Rancher version was this tested on?

@Napsty , the testing was done with master-head version which is basically the latest in-development version and it doesn't have a formal version number like 2.5.9 (see https://hub.docker.com/r/rancher/rancher/tags?page=1&ordering=last_updated). This fix is slated to go into the next release (2.6.0) and also backported into next 2.5.x release (2.5.10) per https://github.com/rancher/rancher/issues/33762.
Hope this helps.

@snasovich Thanks, yes this helps. So will keep my hopes up for 2.5.10 :-)

Did some additional testing and I was unable to install Rancher 2.5 Single Install in a Ubuntu 18.04 and 20.04 KVM (not LXC), due to the nf_conntrack_max permission denied error. Tested with both 2.5.9 and 2.5.8 - same error. According to the support matrix (https://rancher.com/support-maintenance-terms/all-supported-versions/rancher-v2.5.9/) this should work.
Installation of Rancher 2.4.16 works.
For the sake of other people trying to install 2.5.x and failing, please re-open this ticket as the bug is as of the current available releases still existing. Close it when the fix was released and is available. It's just confusing right now. Thanks in advance.

Close it when the fix was released and is available. It's just confusing right now

Hi @Napsty. Are you suggesting that we keep the issue open to track the k8s upstream fix?

Hi @nickgerace
No, only keep the issue open until the Rancher 2.5.x release with the fix (for Single Install) is out .
As the issue title mentions and what the issue initially was filed for, was concerning the 2.5.x Single Install (on Docker).
The k8s upstream fix is a wider issue, as mentioned by @briandowns in https://github.com/kubernetes/kubernetes/pull/103174#issuecomment-890100905. Not sure if it's helpful to keep this Rancher issue open to track the k8s upstream. Doesn't seem to be moving really there (unfortunately).
I'm open for other suggestions of course.

@Napsty , thank you for the additional information. Regarding leaving the issue open, our current process is to close the issues as soon as they are validated by QA on master-head image (for latest upcoming release) or related 2.x - head image (for backports to 2.x releases). Milestone value can then be used to determine where the fix is/will be available.
Note the issue to get this into 2.5.10 is https://github.com/rancher/rancher/issues/33762

@snasovich that's fine, but can you please update the milestone of this issue to 2.5.10? right now it's v2.6.

@Napsty , https://github.com/rancher/rancher/issues/33762 is backport of this issue that targets milestone 2.5.10.

Why is this closed? I just installed rancher:latest and it's broken.

@lindhe , at this time rancher:latest tag is the same as v2.5.9 release and it doesn't have this issue. This will be fixed in the upcoming v2.6.0 release. It is also planned to be backported to next v2.5.x release (v2.5.10) as per separate backport issue https://github.com/rancher/rancher/issues/33762.
Please also note our current process is to close issues once they are validated by QA in internal/RC builds as per this comment - https://github.com/rancher/rancher/issues/33360#issuecomment-892777075.
Hope this helps with clearing things out.

authors: Napsty lindhe nickgerace snasovich sowmyav27


text:
Amazon EC2 node driver clusters are stuck in provisioning

Rancher Server Setup

Rancher version: 2.6-head commit id: 8898bf8
Installation option (Docker install/Helm Chart): Helm

If Helm Chart, Kubernetes Info:
Cluster Type (RKE1, RKE2, k3s, EKS, etc): RKE1
Node Setup: 3 nodes all roles
Version: 1.21.4

Information about the Cluster

Kubernetes version: v1.21.3-rc6+rke2r2
Cluster Type (Local/Downstream): Downstream RKE2 EC2

Describe the bug
Amazon EC2 node driver clusters are stuck in provisioning
To Reproduce

Deployed EC2 rke2 driver clusters with 1 node all roles.
Cluster is stuck in Provisioning

Note:

But i was able to deploy a couple of clusters that came up Active in same Rancher setup.
VPC/Subnet in the node pool was being changed
API request did have the VPC/SG sent by the UI
No other error on the cluster or the machine pool
Nothing obvious from journalctl logs

Did you compare the VPC/Subnets to ensure the security groups had the same ports open and available?
Is it a specifc VPC/subnet?

@sowmyav27 We should really only be testing using the default rancher-machine security group that Rancher creates as well as testing if you come from an upgraded setup that had an old rancher-machine and you re-use it, it still works.

I am not able to reproduce this. I tried using different VPCs and subnets, but was always able to successfully provision a cluster in EC2.

On 2.6-head commit id: b8a44fa
Fresh Install use case.
I am not able to reproduce this issue.

authors: deniseschannon sowmyav27 thedadams


text:
SSL verify False, doesn't work on S3-compatible storage option.

Setup with Minio.
Issue description:
x509: certificate signed by unknown authority, requeuing
errors, even when skip TLS verify is selected
Business impact:
This has impacted Optus in setting up their Rancher DR strategy
I have provided a workaround with persistent volumes, however they want to use Minio in future
Troubleshooting steps:
Tried with TLS verify on and off, same result
Repro steps:
setup backup job on Minio without certs
try to backup

Actual behavior:

Expected behavior:
TLS verify should skip ignore the self signed certificates
See original ticket for logs.
SURE-3153

This needs to be reproduced in 2023-Q1-2.6x and 2023-Q1-2.7x

Working with @eliyamlevy, I was unable to reproduce this issue on v2.7-head or v2.6-head. In both cases, using a self-signed SSL certificate in front of minio, the backup fails as expected with "Skip TLS Verifications" unchecked, and succeeds with "Skip TLS Verifications" checked. This appears to be fixed in the latest builds of both release branches.

Fixed in https://github.com/rancher/backup-restore-operator/issues/254

authors: MKlimuszka nflynt superseb


text:
k8s 1.31 support for Istio

Add k8s 1.31 support for Istio

As of now, the latest version of Istio does not support k8s 1.31. We will need to wait for upstream to add support.

Heads up, Istio 1.24 now supports 1.31

authors: Sahota1225 brosef diogoasouza


text:
When trying to add invalid user/group to  site access , there is no error message presented to user.

Rancher versions: v1.6.8-rc3
AD Auth enabled setup.
Steps to reproduce the problem:
Try to add invalid  user/group to  site access.
The invalid  user/group does not get added to the "Authorized Users and Organizations" list but there is no error message presented to the user which is confusing.
When trying to add invalid  user/group to environment access control , user is provided with error message- Identity not found: <user/group name>.
We should provide the same user experience when adding invalid  user/group to  site access.

Available in v1.6.8-rc5

Version - v1.6.8-rc5
Verified fixed.

authors: deniseschannon sangeethah tfiduccia


text:
rename func

rename func in /pkg/pipeline/remote/gitlab/gitlab.go

LGTM


text:
[2.8] Use plugins/docker for ltsc2022 publish events

Issue: https://github.com/rancher/rancher/issues/44401
Problem
The windows-ltsc2022 pipeline stage uses the rancher/drone-images image to publish images to dockerhub. It seems this approach was taken a few years ago due to drone not publishing ltsc2022 tags of the plugins/docker image. Unfortunately documentation on how the rancher/drone-images image works, and what its settings are, seems to have been misplaced. This makes it difficult to update.
Solution
In the past year ltsc2022 tags of the plugins/docker drone image have been published. This means we can standardize the ltsc2022 stage to use the same image as other pipeline stages which publish docker images.
Testing
This change was tested on the 2.7.11 branch and I confirmed that images were pushed without issue https://drone-publish.rancher.io/rancher/rancher/11509/8/4
Engineering Testing
Manual Testing

Automated Testing
QA Testing Considerations
Regressions Considerations
Existing / newly added automated tests that provide evidence there are no regressions:

I'm going to close this PR since we are migrating away from drone towards github actions in the near future and the existing rancher/drone-images plugin is working as expected


text:
Log underlying error when YAML generation fails

Fixes #99 with best-effort.
I can't actually manage to hit an error like the on from https://github.com/rancher/support-bundle-kit/issues/99#issue-2215521652 in my cluster. I tried mangling the cluster-admin ClusterRole to remove access to nonResourceURLs and removing the system:discovery ClusterRoleBinding in an attempt to stop support-bundle-manager from using the Kubernetes Discovery API. This DID result in a support bundle without YAML files, but did not trigger the Unable to fetch cluster resources message (in either a modified or unmodified support-bundle-kit). This means I cannot actually show the result of this PR in action. However, it should provide us additional debugging information if the YAML collection fails again like this in the future.

@ejweber, could you help to rebase for the conflict?

It looks like @ibrokethecloud beat me to some of these locations, but I think these errors also make sense in the error log, so we should move forward with the changes IMO. Rebased and fixed conflicts.

authors: Vicente-Cheng ejweber

repo: rancher/support-bundle-kit


text:
Trying to get an IP address automatically for all interfaces at boot time.

This process extends the startup process.
Automatic IP undistributed a network in this process is even longer.
Network settings must be set by the user. or to get an IP address automatically is only open for the first interface will be more accurate.
System: VirtualBox

The networking is configurable through the rancher.yml and cloud-init.  The documentation is at https://github.com/rancherio/os/blob/master/docs/config.md#networking.  In the /var/lib/rancher/conf/rancher.yml you will need to do something like:
network:
  interfaces:
    eth*:
      # Disable DHCP for all interfaces
      dhcp: false
    eth1:
      address: 192.168.0.5
      gateway: 192.168.0.1

If you are using the cloud-init, do the same as above but nest everything under the rancher key.

In v0.3.0, this should be fixed. Please re-open if it's still an issue.

authors: deniseschannon fatihusta ibuildthecloud

repo: rancherio/os


text:
Environment members are wrong if GitHub url is changed

v0.22.0-rc1
Steps:

Authenticate as regular GitHub user
Create multiple Environments, giving random owner/member access to rancherdev & rancherdev2
Disable Access Control
Authenticate as Enterprise user

Results:
If you go to Manage Environments and check the Environments, you will see you are owner to them all, but if you click on drop-down there is only one.
Expected:
All Environments should show up in drop-down that you are owner to.

@will-chan I think this should move to 1.0.  It's probably not a very common use case to switch GitHub URLs, and it's not very clear what we should do with old project member records if you do.

Closing and added to #5450 for single point of reference

repo: rancherio/rancher


text:
as a clusternator user I do not want to see (seemingly) pointless error messages when log/ssh/log-ecs commands complete

Sometimes when killing off a tail log (either clusternator log, or clusternator log-ecs) with ctrl+c the process exits as expected, but a JavaScript error is logged to console, this is not desirable.
This also sometimes happens when clusternator ssh is terminated with ctrl+d (EOF)

I'm not sure of the underlying cause of the error yet, but all of the cases should now be printing messages instead of stack traces.

repo: rangle/the-clusternator

license: mit


text:
[1.12+] Add configuration option to change energy capacity of items

Hello.
Firstly, thank you for your mods.
I've have simple suggestion. It's possible to change energy usage of different items in mod (such as Wireless Grid), but energy capacity value is hardcoded:
https://github.com/raoulvdberge/refinedstorage/blob/mc1.12/src/main/java/com/raoulvdberge/refinedstorage/item/ItemEnergyItem.java#L19
Please, add configuration option to change energy storage of items, which can store/use energy.
/* MC 1.12+ */

True, I've wanted to do this... But I do need to add client <-> server config syncing for that.

authors: OneEyeMaker raoulvdberge

repo: raoulvdberge/refinedstorage


text:
[Suggestion] Operators in Crafting Request

Suggestion description:
Allow us to put operators in the crafting request menu.
What happens:
When you put * it will multiply the numbers, / will integer divide, - subtract, + add and possibly ^ will power it. Would follow basic operation order, allow brackets etc. This is useful when, for example you want to build multiple of the same multiblock structure and you want to do it easily.
Steps to reproduce:

Place the numbers in with the operators
Press craft
Will craft that amount

Version:

Minecraft: Any/All
Forge: Any/All
Refined Storage: Any/All

I like the idea, but it's more work than it's worth.

authors: DownLoude raoulvdberge


text:
[FEA] add variable indicating the upstream scikit-image version that cucim.skimage matches

Is your feature request related to a problem? Please describe.
cucim.skimage currently mirrors the API of skimage 0.18.x. Given that the cuCIM version number is unrelated to the scikit-image one, it would be useful to define some kind of variable that users could query to determine what version of the upstream scikit-image API we are compatible with.
Describe the solution you'd like
Add a variable like cucim.skimage.__api_version__ that would currently be '0.18' and can be updated accordingly as we update our implementations in sync with upstream scikit-image. We can likely also make this correspondence between versions clear in the online documentation.
Describe alternatives you've considered
Additional context
A scikit-image 0.19 release will occur in the very near term, but it will still take a bit of time to backport API changes/deprecations here, so this could lead to some user confusion in the intermediate term.

Looks like PR ( https://github.com/rapidsai/cucim/pull/172 ) was implementing this
Would this be useful for the dispatching work Greg?

repo: rapidsai/cucim


text:
Avoid the use of shared variable.

Use register instead.
Fix Python benchmark script with latest pandas and XGBoost.

I ran the Python benchmark script using RTX8000 with CPU excluded:
PR

model
test_rows
cpu_time(s)
cpu_std
gpu_time(s)
gpu_std
speedup

adult-small
10000
0.0

0.011279034591279925
0.0071617705732274824

adult-med
10000
0.0

0.11670323801226914
0.011867081750644454

adult-large
10000
0.0

9.429356226988602
0.047229702183655395

covtype-small
10000
0.0

0.01151795060141012
0.003561754665202217

covtype-med
10000
0.0

0.6641728987917304
0.0032803489983452214

covtype-large
10000
0.0

74.24905845939648
0.5906834845783823

cal_housing-small
10000
0.0

0.006276315008290112
0.002279411050170562

cal_housing-med
10000
0.0

0.10911295339465141
0.0012658547831405737

cal_housing-large
10000
0.0

23.429275520995724
0.08867194402118761

fashion_mnist-small
10000
0.0

0.16429676760453732
0.06816532400946669

fashion_mnist-med
10000
0.0

4.30540003181668
0.07100682231932201

fashion_mnist-large
10000
0.0

178.59231641321676
1.0623992933829536

main

model
test_rows
cpu_time(s)
cpu_std
gpu_time(s)
gpu_std
speedup

adult-small
10000
0.0

0.010922096599824727
0.006964535125901965

adult-med
10000
0.0

0.11171154719777406
0.012917956737291719

adult-large
10000
0.0

9.12171239000745
0.16260832207140813

covtype-small
10000
0.0

0.011427397408988326
0.003081750313730569

covtype-med
10000
0.0

0.6582016726024449
0.010074246049065491

covtype-large
10000
0.0

73.67104159318842
0.6321216129573327

cal_housing-small
10000
0.0

0.005807545990683139
0.00245267488361271

cal_housing-med
10000
0.0

0.10978057580068708
0.0016856217806583914

cal_housing-large
10000
0.0

23.66984584759921
0.10060247707348238

fashion_mnist-small
10000
0.0

0.1685630762251094
0.06951830276227733

fashion_mnist-med
10000
0.0

4.44043413939653
0.06073396821402969

fashion_mnist-large
10000
0.0

183.3073539715959
0.6199842390017297

@hcho3 Have you seen this error using the rapids test matrix generator:
  File "/opt/conda/lib/python3.11/site-packages/rapids_dependency_file_generator/_rapids_dependency_file_generator.py", line 421, in make_dependency_files
    raise ValueError(f"No matching matrix found in '{include}' for: {matrix_combo}")
ValueError: No matching matrix found in 'cuda_version' for: {'cuda': '12.5', 'arch': 'x86_64', 'py': '3.11'}

with rapidsai/shared-workflows/.github/workflows/conda-cpp-tests.yaml?

The failure on this PR is due to the addition of CUDA 12.5 support. This repository was missed during the upgrade. https://github.com/rapidsai/build-planning/issues/73
I went ahead and pushed the changes you need in 444005e3e2c21b9d87526d114c44989754704f40.

I also pushed commit e04ea9b288a9691ce47383862bb3b15dee92f060 with the changes from ci/release/update-version.sh 24.10.00. This repo is updated pretty irregularly and we need to keep all the RAPIDS versions aligned (not just the CI workflow branches).

authors: bdice trivialfis

repo: rapidsai/gputreeshap


text:
rapids_cpm_thrust doesn't place temp file in a searched location

This makes sure that find_package(Thrust) which searches a build directory doesn't accidentally use files meant for installation.

@gpucibot merge

repo: rapidsai/rapids-cmake


text:
Try any failing tests up to 3 times to guard against network issues

Description
rapids-cmake has seen network issues when downloading files from GitHub. We will try tests up to 3 times when they fail to validate the issue isn't a poor network.
Checklist

[x] I am familiar with the Contributing Guidelines.
[x] New or existing tests cover these changes.
[x] The documentation is up to date with these changes.

I really want this fix since my PR #637 has been failing repeatedly due to network issues. I pushed a commit to fix a flag -- hope that's alright @robertmaynard.

authors: bdice robertmaynard


text:
Just Entity to Table on the Lookup DIalog

Just updates from Entity to table

Removing { .. } for oneliners is too radical for my taste.... 🙄

Removing { .. } for oneliners is too radical for my taste.... 🙄

license: MIT


text:
Do restaking

метод restaking покрыл тестами.
метод рабочий

Better to see next PR doRestakeAndDelegation

repo: rariblecom/protocol-contracts


text:
Add debug/performance stats to the bottom of the responses?

On of the big worries with anything like this is "is it fast enough" and of course "is it optimised" or "where should I optimise". Wonder if we should return some stats on time taken to generate a query and number SQL statements etc. (if possible to get) in the response?
Could either toggle this globally via umbracoDebug or per query I guess?

Newer versions of GraphQL for .NET added support for Apollo Tracing which gives you per field metrics. You can see an example of the output here
I've upgraded the project and added an option to enable metrics by passing EnableMetrics = true to the GraphQLServerOptions in the UseUmbracoGraphQL call.
It might be possible to hook into the MiniProfiler and expose it as an extension as well.

Was discussing with with @ste today. Great to see. He's playing with a way for format the results some more. Was thinking of an option to just "include everything" and then a GraphQL way using fragments to only pull in what your want or some helper fragments (briefStats or verboseStats or something like that).
Need to be careful we aren't duplicating effort though ;)

authors: PeteDuncanson rasmusjp

repo: rasmusjp/umbraco-graphql


text:
How can I add text to a photo? For example, adding the shooting time to the photo.[HOW-TO]

How can I add text to a photo? For example, adding the shooting time to the photo.

Hi, you could use OpenCV's cv2.putText method to draw text on the image (numpy array) that you have captured. There should be lots of examples of this online. You could then save it using cv2.imwrite.
Alternatively you could put the text on every single image, such as in this example. Although that's a video example, the technique using the callback should work just the same for still images.


text:
Board definition header files for the iniital set of SparkFun rp2040 …

Header board definition files for the SparkFun rp2040 boards:

rp2040 ProMicro
rp2040 Thing Plus
rp2040 MicroMod

continued in #192

authors: kilograham kirk-sfe

repo: raspberrypi/pico-sdk


text:
Fixes #1666

This PR adds support for the iLabs OpenDec02 board by adding the ilabs_opendec02.h header file with specific settings for that particular board.

fixes #1666

authors: PontusO kilograham


text:
🛑 OSDN Mirror (osdn.dl.osdn.net) is down

In 00b1c8b, OSDN Mirror (osdn.dl.osdn.net) (https://osdn.dl.osdn.net) was down:

HTTP code: 0
Response time: 0 ms

Resolved: OSDN Mirror (osdn.dl.osdn.net) is back up in defa1fa.

repo: raspbian-addons/status


text:
🛑 OSDN Mirror (osdn.dl.osdn.net) is down

In 1afc175, OSDN Mirror (osdn.dl.osdn.net) (https://osdn.dl.osdn.net) was down:

HTTP code: 0
Response time: 0 ms

Resolved: OSDN Mirror (osdn.dl.osdn.net) is back up in 108602f.


text:
Update JoinMarket to v0.9.10

What & Why
New JoinMarket release is available for more than month, update to it. Most imoprtant changes - adds RBF fee bumping script and has RPC API improvements that will be needed for Jam version update.
Also removed my tippin.me link (which was copied from my old guide outside this repo), last time checked I couldn't withdraw sats from there anyway. And not often people donated anyway.
Scope

[ ] significant change to core configuration
[X] independent bonus guide
[ ] simple bug fix

Anyone plan to review / test this? @Mynima? @Buttafuoco? @VajraOfIndra? @sig-noi?

ACK. Been running 0.9.10 for a little more than a month without issue

IMHO this is ready to merge, release is two months old and seems to be working for everybody. But needs GitHub ACK from somebody, RaspiBolt repo settings doesn't allow to merge commits without at least one approving review.

@pleb4868 @Mynima Could somebody do "Approve" here? :)

repo: raspibolt/raspibolt


text:
Same responses even when code changes

I am using ratchet with zmq to connect to a WAMP Autobahn v0.8 front-end.
Everything works perfectly however when I change the topic code, the responses do not change!
i am running this in docker, when I restart the containers the updated responses get updated but then if I change this again nothing changes!
It is as if the responses are being cached, but I don't know where or why

Did you restart the application after the code change? If so, please post code so others are able to reproduce the issue.

authors: cboden hussan-choudhry

repo: ratchetphp/Ratchet


text:
Banner ads "Internal error" showing but Interstitial ad showing perfectly

document.addEventListener('deviceready', function() {
admob.banner.config({
id: admobid.banner,
isTesting: true,
autoShow: true,
})
admob.banner.prepare()
admob.interstitial.config({
id: admobid.interstitial,
isTesting: false,
autoShow: false,
})
admob.interstitial.prepare()
}, false)
document.addEventListener('admob.banner.events.LOAD_FAIL', function(event) {
console.log(event)
})
document.addEventListener('admob.interstitial.events.LOAD_FAIL', function(event) {
console.log(event)
})
document.addEventListener('admob.interstitial.events.LOAD', function(event) {
console.log(event)
document.getElementById('showAd').disabled = false
})
document.addEventListener('admob.interstitial.events.CLOSE', function(event) {
console.log(event)
admob.interstitial.prepare()
})
interstitial ad are showing perfectly  but banner ad is not showing but for test ads it show always.
error:0 Internal error occur when i insert my publisher id.
at starting it showed banner ad but after closing the app and opening it again no banner ad displayed

Had this same problem but figured it out. Instead of admob.banner.config({ id: admobid.banner, isTesting: true, autoShow: true, }) and admob.banner.prepare(), just do admob.banner.prepare({ id: admobid.banner, isTesting: true, autoShow: true, }).

I tried passing arguments to admob.banner.prepare but it gives me a typescript error saying .prepare isn't expecting arguments. Any other solutions work for you guys?

I solved and documented here::
https://github.com/manoharreddyporeddy/everyday-solutions/blob/master/display-ads-on-android-using-admob.js

repo: ratson/cordova-plugin-admob-free


text:
Update pom.xml

Updated pom.xml file for review and approval

Closing request

authors: itsmesubbu raunakkankaria

repo: raunakkankaria/jpetstore


text:
Added option to colorize messages the same color as the sending nick …

…(defaults to off)
Added new option 'colorize_messages' that defaults to off, that when turned on will result in all messages being colored the same as the nick of the sender. Doesn't interfere with coloring usernames in the messages, and I've added corresponding doc to the README.
Example:

I missed this a lot when moving to wee-slack from using the irc gateway + a bouncer. This option effectively mimics the behavior of the 'colorize_lines.pl' plugin.

I think having this would be good, but as you mention, there's a plugin that does this already. Do you know what it'd take for that one to just be able to do what it wants directly, rather than effectively reimplementing it in weeslack?

I agree, that would me a much more ideal solution. The main reason I took this route is because wee-slack seems to do a lot on it's own (colorizing nicks, hard-coding mention highlights), and doesn't seem to play nice with number of plugins & and features (colorized_lines, custom highlight words, etc) built into wee-slack. I imagine this is mostly due to the fact that the buffer frequently changes and behaves in different ways than normal irc, and all data is being provided by an external source.
If you look at all three of my pull requests, they're essentially adding / fixing behavior that's already implemented elsewhere in weechat. It'd be great to hook into this functionality directly in wee-slack, and maybe implement some buffer related hooks (if they exist), so that other normal buffer altering plugins will play nicely.
I'm a very new weechat user and not familiar at all the how plugins work or tie into weechat in a technical sense, the above is just based on observation. All that being said, when I get a chance I'll try and dig a little deeper to see if there's a good way to hook into the functionality for 'colorized_lines.pl' and if possible, work on finding a way so that buffer related plugins can play nicely with wee-slack's buffers.

This works fine for me. Merging - thanks!

authors: gilbertw1 rawdigits tfheen

repo: rawdigits/wee-slack


text:
Fix cluster resource detection in multi-node clusters for number_actors < number_nodes

When starting 4 distributed actors on a 8 node cluster with 16 CPUs each (144 CPUs), we autodetect 36 CPUs and schedule a placement group with 4 bundles a 36 CPUs.
Instead we should be smart about this and only assign 16 CPUs per worker (and maybe throw a warning that the cluster will be underutilized).
cc @mmui would you be interested in taking this?

I feel it's worth pointing out that we seem to be already doing this:
def _autodetect_resources(ray_params: RayParams,
                          use_tree_method: bool = False) -> Tuple[int, int]:
    gpus_per_actor = ray_params.gpus_per_actor
    cpus_per_actor = ray_params.cpus_per_actor

    # Automatically set gpus_per_actor if left at the default value
    if gpus_per_actor == -1:
        gpus_per_actor = 0
        if use_tree_method:
            gpus_per_actor = 1

    # Automatically set cpus_per_actor if left at the default value
    # Will be set to the number of cluster CPUs divided by the number of
    # actors, bounded by the minimum number of CPUs across actors nodes.
    if cpus_per_actor <= 0:
        cluster_cpus = _ray_get_cluster_cpus() or 1
        cpus_per_actor = max(
            1,
            min(
                int(_get_min_node_cpus() or 1),
                int(cluster_cpus // ray_params.num_actors)))
    return cpus_per_actor, gpus_per_actor

def _get_min_node_cpus():
   max_node_cpus = min(
       node.get("Resources", {}).get("CPU", 0.0) for node in ray.nodes())
   return max_node_cpus if max_node_cpus > 0.0 else _ray_get_cluster_cpus()

I don't think we are testing it, though.

Maybe we just need
def _get_min_node_cpus():
   max_node_cpus = min(
       node.get("Resources", {}).get("CPU", 0.0) for node in ray.nodes() if node.get("Alive", False))
   return max_node_cpus if max_node_cpus > 0.0 else _ray_get_cluster_cpus()

It seems if just one Node reports 0.0 resources, we will default to _ray_get_cluster_cpus(). Also, we should probably default to 1 then?

1 would be a much safer fallback. Let me quickly test this out

@krfricke I tested it and your proposed change solves the problem we were facing.

Awesome, I'll file a quick PR


text:
Configure automated testing, linting, and formatting of pushed code

Implement automated testing, linting, and formatting of code pushed to repo

Black for formatting
Pylint for linting
Pytest to run test cases

Automated testing, and lint / format check added


text:
[Arc]...some mistake with "search tab" command.

Extension
https://raycast.com/the-browser-company/arc
Description
Error:
SyntaxError: Unexpected token '’', ..."ни здоров\’я є найкр"... is not valid JSON
    at JSON.parse (<anonymous>)
    at Object.T5 [as current] (/Users/arsenpetrosov/.config/raycast/extensions/606e26d8-b3c5-4760-8001-dccce1b872c4/search-tabs.js:89:20)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

Steps To Reproduce
I've only selected option "Search Tabs" and've got the mistake.
Current Behaviour
No response
Expected Behaviour
No response

+1

There's still ongoing issues with any commands related to Tabs. Tried again today to go to a tab via the command, and it'll just open a tab with a blank screen. Very odd.

Thanks for bringing this up. It appears that this is a duplicate of issue https://github.com/raycast/extensions/issues/9758, so I'll mark it as such.

repo: raycast/extensions


text:
[I Don't Have Spotify] Spotify link not being validated properly

Extension
https://www.raycast.com/sjdonado/idonthavespotify
Raycast Version
1.80.0
macOS Version
14.5
Description
I pasted a Spotify link (specifically this one: https://open.spotify.com/album/3kjHLu1pL7tdY88GFwEkl6?si=oVIZ-ZbfQM2S1M7IM1f6RQ) and got an error that printed some json output saying it isn't valid.

Steps To Reproduce

Have Spotify link in clipboard
Launch the extension

Current Behaviour
throws error
Expected Behaviour
validates link and shows other sources

Fixed already https://github.com/raycast/extensions/pull/13494
@raycastbot close this issue

authors: brunocbreis sjdonado


text:
[Pixabay] Search Music, Search Sound Effects, Search Photos[?], Search Vectors[?], Search Illustrations[?]

Extension
https://www.raycast.com/tonka3000/pixabay
Description
Expand the search categories:
Right now there is search Videos and search Images.
It would be great to be able to search Music and Sound Effects.
(Not as important) Maybe break down Images into:
-Photos
-Illustrations
-Vectors
Who will benefit from this feature?
Anyone who might be looking to find and use copyright-free music and sound effects.
Likely a large number of the users who already use the extension.
Anything else?
No response

Hi @escoolioinglesias ,
Searching for music is not possible via the API, only images and videos AFAIK.
Switching between photo, illustration and vector should be doable via the menu in the top right corner.
Greetings