Error response from daemon: error unmarshalling content: unexpected end of JSON input


It happened the other day that one user reported that he was unable to pull a docker image from an internal registry. So I tried from my laptop, it looked fine at the first beginning. There were a few downloading processed going on, but it threw the error unknown blob at the end. So I tried … Continue reading Error response from daemon: error unmarshalling content: unexpected end of JSON input

Advertisements

VT-x is not available caused by Docker for Windows


If you are trying to run Virtualbox on Windows, and received the error 'VT-x is not available (VERR_VMX_NO_VMX)'. Normally, the first thing is to check if the processor supports VT-x. If yes, then to see whether it has been enabled in BIOS? If yes, but you are still seeing this error. Then another possible reason … Continue reading VT-x is not available caused by Docker for Windows

Pods are not recreated after kubernetes node failure


  We had a short outage recently which was caused by the pods were not recreated on other nodes when the previous node become unresponsive. It is Kubernetes 1.6, and according to the documentation, it is expected in some cases. "If the Status of the Ready condition is “Unknown” or “False” for longer than the … Continue reading Pods are not recreated after kubernetes node failure

Autoscaler on OpenShift Dedicated


At the time of writing, OpenShift dedicated (v3.5.5.31) only supports autoscaling based on the CPU metrics. So the first step is to ensure the CPU request is in place. It can be setup in the section of container spec. e.g spec: containers: image: 'poc/web' name: my-web ports: - containerPort: 3000 resources: requests: cpu: 200m limits: … Continue reading Autoscaler on OpenShift Dedicated