trow: manifest invalid error

I have a K8s cluster setup with the following

• Trow version v0.3.0
• Metal LB v0.9.3
• K8s version - Oracle K8s v1.12.10+1.0.12.el7
• Docker version - 19.03.11-ol
• OS: Oracle Linux Server 7.6 (RHEL 7.6)

After setting it up with a non-TLS version, I tagged one of the nginx images and attempted to push it. However, I was faced with the “manifest invalid” error.

[user@machine1 test]$ sudo docker push privregisty.client.com/test/nginx:1.19.1-alpine The push refers to repository [privregisty.client.com/test/nginx] 689cc6c05bc7: Layer already exists b7d86c86e432: Layer already exists 08fb2e2ff084: Layer already exists 5f1add6e505b: Layer already exists 3e207b409db3: Layer already exists manifest invalid I tried with trow v0.2.0 to check if it was an issue with the image and this time around, it went in but with a warning message.

[user@machine1 test]$ sudo docker push privregisty.client.com/test/nginx:1.19.1-alpine The push refers to repository [privregisty.client.com/test/nginx] 689cc6c05bc7: Layer already exists b7d86c86e432: Layer already exists 08fb2e2ff084: Layer already exists 5f1add6e505b: Layer already exists 3e207b409db3: Layer already exists [DEPRECATION NOTICE] registry v2 schema1 support will be removed in an upcoming release. Please contact admins of the privregisty.client.com registry NOW to avoid future disruption. More information at https://docs.docker.com/registry/spec/deprecated-schema-v1/ 1.19.1-alpine: digest: sha256:0eb4a858daf2ee76b19819cc76998aea95a6c73984449c914be5447e2b27151d size: 12646

I’m now trying to build trow on my local and try if that works. Is there an issue with the current v0.3.0 image of trow with docker 18.0+ ?