chore(deps): update quay.io/cilium/json-mock docker tag to v1.3.8

[renovate]

This PR contains the following updates:

Package	Update	Change
quay.io/cilium/json-mock	patch	v1.3.6 -> v1.3.8

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Never, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[tklauser]

In all failing workflows the echo-same-node pods using the new json-mock image are failing to become ready. I assume this is due to the changes in the new version, namely cilium/json-mock#144? cc @giorio94

[giorio94]

In all failing workflows the echo-same-node pods using the new json-mock image are failing to become ready. I assume this is due to the changes in the new version, namely cilium/json-mock#144? cc @giorio94

Yes, although I haven't yet figured out the reason. The image built from my PR works correctly, while the one from the release doesn't (there are no additional commits there). I assume that some underlying component must have changed in the meanwhile.

$ docker run -e PORT=8080 quay.io/cilium/json-mock-ci:5d5776ab3730393c0fc7a3f884452f18bfcac616 # works as expected
$ docker run -e PORT=8080 quay.io/cilium/json-mock-ci:93b660294967f9fc1df1e41ea2a31ce50578b489 # fails

[giorio94]

The difference is the json-server version which is installed:

# Working:
npm list -g
/usr/local/lib
+-- corepack@0.23.0
+-- json-server@0.17.4
`-- npm@10.2.4

# Not working:
npm list -g
/usr/local/lib
+-- corepack@0.23.0
+-- json-server@1.0.0-alpha.14
`-- npm@10.2.4

[giorio94]

I've opened cilium/json-mock#146 to fix it.