🆕 https://github.com/k3d-io/k3d/releases/tag/v5.5.0 🆕 # v5.5.0 - 17.05.2023 ### Added - Add support for ulimits (#1264) - new flag:

k3d cluster create --runtime-ulimit NAME[=SOFT]:[HARD]

(same for

k3d node create

) - add: K3D_FIX_MOUNTS fix to make / rshared (e.g. to make Cilium work) (#1268) - new environment variable:

K3D_FIX_MOUNTS=1

- add(docs): podman instructions for macOS (#1257) - Adds json response of version info (#1262) - new flag:

k3d version -o json

### Changed - change: allow full K3s registry configuration (#1215) - change: update deps (manual + dependabot) - change: set e2e test ghaction timeout - change: improved help text for k3d version ls - change: deprecate 'k3d version ls --format' in favor of '--output' - change: golangci-lint fix whitespaces - change: udpate docs ### Fixed - Fix panic when k3sURLEnvIndex is -1 (#1252) - Fix spelling mistake in configfile.md (#1261) - Correct typo: Inconsistent filename in registry documentation. (#1275) - fix: k3d version ls (now via crane) (#1286) - fix: registries.yaml file not marshalled correctly by k8s yaml package ### Deprecated - change: deprecate 'k3d version ls --format' in favor of '--output' ## New Contributors * @breezy-pharmacist-36696 made their first contribution in https://github.com/k3d-io/k3d/pull/1264 * @maxsargentdev made their first contribution in https://github.com/k3d-io/k3d/pull/1215 * @shoffmeister made their first contribution in https://github.com/k3d-io/k3d/pull/1261 * @aescaler-raft made their first contribution in https://github.com/k3d-io/k3d/pull/1257 * @bafzachris made their first contribution in https://github.com/k3d-io/k3d/pull/1275 * @dgershman made their first contribution in https://github.com/k3d-io/k3d/pull/1262 Full Changelog: https://github.com/k3d-io/k3d/compare/v5.4.9...v5.5.0

5.5.0 has a regression with local docker registry images can not be pulled from it using

localhost:5000

looks like this mapping not working

mirrors:
          "localhost:5000":
            endpoint:
              - <http://k3d-registry:5000>

Which version of k3s are you using with it?

I don't pin it, the one that picked up by default by k3d

That's weird, if it wasn't working, the release should have failed on the e2e tests. In fact it wasn't working before the release during my tests (made the tests hanging)

sent kubectl output to private message

Thank you, I'll get back to this soon