Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Drone web app Helm deployment fails because of invalid image #6

Open
larrywa opened this issue Sep 20, 2022 · 5 comments
Open

Drone web app Helm deployment fails because of invalid image #6

larrywa opened this issue Sep 20, 2022 · 5 comments
Assignees

Comments

@larrywa
Copy link

larrywa commented Sep 20, 2022

Error:
Failed to apply default image tag "marketplace.azurecr.io/bitnami/git@": couldn't parse image reference "marketplace.azurecr.io/bitnami/git@": invalid reference format

I've gone through the values.yaml file and updated every image tag to an appropriate image that can be found in Docker but I believe this error means something different. Any idea what its' looking for?

@coffeeneer
Copy link

I've gotten this to work with all the original image versions but changing the 1.x.x. version for the common library to 1.10.0 since that version was mentioned in the exercise. However accessing the load balancer ip showed a nginx 404 page.

@JaimeStill
Copy link

Confirming and adding some context to this issue.

When running everything in the Cloud Shell and following the Deploy the Helm Chart section:

image

Changed the 1.x.x version in Chart.yaml:

image

Updated dependencies then updated the deployment:

image

Navigating to the load balancer:

image

@ckittel
Copy link
Member

ckittel commented Feb 3, 2023

@rayoef & @philmea - just wanted to make sure your AKS content team saw this.

@p1johnson
Copy link

I had the same issue with the invalid image tag and was able to resolve by fixing the version of the common library as @coffeeneer did.

I also experienced the same issue with the 404 Not Found error from Nginx. This is due to the nginx-ingress using host based routing - requests to the ingress need to be in the form http://aspnet-core.local/ to match the host name set in the values file. nginx-ingress does not deal with requests via IP address. As a workaround I was able to get this working by updating my local hosts file to point aspnet-core.local to the public IP address of the ingress. It may be a bit late for you now @JaimeStill to try this?

@zorglob
Copy link

zorglob commented Nov 29, 2023

Issue still present. I was able to get it working, thanks to @coffeeneer and @JaimeStill indicating how to solve the invalid image tag and @p1johnson for the nginx issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants