MockServer enables easy mocking of any system you integrate with via HTTP or HTTPS with clients written in Java, JavaScript and Ruby. MockServer also includes a proxy that introspects all proxied traffic including encrypted SSL traffic and supports Port Forwarding, Web Proxying (i.e. HTTP proxy), HTTPS Tunneling Proxying (using HTTP CONNECT) and SOCKS Proxying (i.e. dynamic port forwarding).
Docker complains that its format is deprecated
`$ docker pull radial/busyboxplus
Using default tag: latest
What's next:
View a summary of image vulnerabilities and recommendations → docker scout quickview radial/busyboxplus
Error response from daemon: [DEPRECATION NOTICE] Docker Image Format v1 and Docker Image manifest version 2, schema 1 support is disabled by default and will be removed in an upcoming release. Suggest the author of docker.io/radial/busyboxplus:latest to upgrade the image to the OCI Format or Docker Image manifest v2, schema 2. More information at https://docs.docker.com/go/deprecated-image-specs/`
Using service-test.yaml also has a negative side effect when MockServer starts and tests pass, but the curl container still cannot start and everything crashes after some timeout (30 minutes in my case). I had this scenario on a Jenkins server with K8S.
Please, use httpGet liveness and readiness probes in helm-chart deployment instead of radial/busyboxplus:curl
helm/mockserver/values.yaml service: test: image: radial/busyboxplus:curl
The Docker image https://hub.docker.com/r/radial/busyboxplus is 9 years old
Docker complains that its format is deprecated `$ docker pull radial/busyboxplus Using default tag: latest
What's next: View a summary of image vulnerabilities and recommendations → docker scout quickview radial/busyboxplus Error response from daemon: [DEPRECATION NOTICE] Docker Image Format v1 and Docker Image manifest version 2, schema 1 support is disabled by default and will be removed in an upcoming release. Suggest the author of docker.io/radial/busyboxplus:latest to upgrade the image to the OCI Format or Docker Image manifest v2, schema 2. More information at https://docs.docker.com/go/deprecated-image-specs/`
https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/ My simple change:
readinessProbe: httpGet: path: /status port: 1080 livenessProbe: httpGet: path: /status port: 1080Using service-test.yaml also has a negative side effect when MockServer starts and tests pass, but the curl container still cannot start and everything crashes after some timeout (30 minutes in my case). I had this scenario on a Jenkins server with K8S.