-
This bug is nearly identical to #3340 which was thought to be specific to Amazon Linux, but this appears on RedHat 8 and Rocky Linux 8.
**What happened**:
Creating a second cluster fails. The me…
-
### Description
There seems to be latency between network create return, and availability of the network - or between the container creation return and the operation attaching it to the network.
…
-
**What happened**:
I tried to create a cluster with two control-plane nodes and I got an error message. Defining only one control-plan node but overall the same number nof nodes works.
> I0803 10…
-
### What happened?
I am trying to bring up kubernetes cluster with containerd and nerdctl.
After bringing up my cluster, I am able to see duplicate entries for nerdctl images
.
- local OCI …
-
**Is this a BUG REPORT or FEATURE REQUEST?**:
> Uncomment only one, leave it on its own line:
>
/kind bug
> /kind feature
**What happened**:
```bash
$ kubectl exec -ti demo-198693184…
-
### Description
nerdctl compose up does not succeed with wsl2 based distros.
### Steps to reproduce the issue
``` cat compose.yaml
services:
web:
build: .
ports:
- "8000…
-
### Description
Hi, I am getting this bug on Lima 0.22.0: https://github.com/rancher-sandbox/rancher-desktop/issues/1600
In my case, the container that triggered it was created with:
lima n…
-
### Description
nerdctl push level=fatal msg=content digest sha256:xxx: not found
### Steps to reproduce the issue
command :
1. nerdctl commit --namespace xxx "${CONTAINER_ID}" "${_IMAGE_INFO}"…