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

Docker image for UI not found #867

Closed
1 of 5 tasks
steveww opened this issue Oct 11, 2021 · 3 comments · Fixed by #902
Closed
1 of 5 tasks

Docker image for UI not found #867

steveww opened this issue Oct 11, 2021 · 3 comments · Fixed by #902
Assignees
Labels
bug Something isn't working customer issue severity/high low < medium < high < critical

Comments

@steveww
Copy link

steveww commented Oct 11, 2021

Describe the bug
ghcr.io/weaveworks/wego-app:0.3.1 image does not exist

$ gitops version

Current Version: 0.3.1
GitCommit: 290154c
BuildTime: 2021-10-08T22:03:28Z
Branch: HEAD
Flux Version: v0.17.2

Environment

  • gitops: [e.g. v0.3.1]
  • kubernetes: [e.g. 1.20.4]
    • KinD - version]
    • k3s - version
    • cloud [e.g., EKS, AKS] version
    • other - name version
    • All of the above
  • Browser + version: [e.g. chrome 74, safari 12, firefox 87]

Affects versions

To Reproduce
gitops install

K8s fails to pull image for UI because it does not exist.

Expected behavior
Docker image exists

Config and Logs

@jpellizzari jpellizzari added the bug Something isn't working label Oct 12, 2021
@jpellizzari jpellizzari added the qa label Oct 12, 2021
@jpellizzari
Copy link
Contributor

Adding a QA label so we know to add some test coverage here.

@steveww
Copy link
Author

steveww commented Oct 14, 2021

Docker image for 0.3.1 still has not been pushed.

docker pull ghcr.io/weaveworks/wego-app:0.3.1
Error response from daemon: manifest unknown

@luizbafilho
Copy link
Contributor

Hey @steveww for now can you add a v to the image manually? the docker pull ghcr.io/weaveworks/wego-app:v0.3.1 has been published properly.

We'll fix the deployment template in the next release.

@JamWils JamWils added severity/critical low < medium < high < critical severity/high low < medium < high < critical and removed severity/critical low < medium < high < critical labels Oct 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working customer issue severity/high low < medium < high < critical
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants