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

GoPhish Chart Broken #49

Open
PMcLeanGLX opened this issue Jun 26, 2024 · 4 comments · May be fixed by #51
Open

GoPhish Chart Broken #49

PMcLeanGLX opened this issue Jun 26, 2024 · 4 comments · May be fixed by #51
Assignees
Labels
bug Something isn't working

Comments

@PMcLeanGLX
Copy link

Failed to pull image "josaorg/gophish:0.12.1": failed to pull and unpack image "docker.io/josaorg/gophish:0.12.1": failed to resolve reference "docker.io/josaorg/gophish:0.12.1": unexpected status from HEAD request to https://www.docker.com/: 403 Forbidden

@PMcLeanGLX
Copy link
Author

I fixed the image pull issue by adding tag "latest", but now get a configmap "gophish-config" not found.

@PMcLeanGLX
Copy link
Author

Fixed the 2nd error by creating a config map myself. Not sure what was stopping the helm chart from doing that.

@PMcLeanGLX
Copy link
Author

But now it cant see the database: "waiting for database to be up..."

@thamudi thamudi linked a pull request Jul 16, 2024 that will close this issue
@thamudi
Copy link
Member

thamudi commented Jul 16, 2024

@PMcLeanGLX
Hello, thanks for bringing this to our attention.
Regarding the remaining issues can you please provide the values you are using in deploying this chart?

You shouldn't need to create a configmap since there is a default configmap.

@thamudi thamudi self-assigned this Jul 16, 2024
@thamudi thamudi added the bug Something isn't working label Jul 16, 2024
@thamudi thamudi linked a pull request Jul 16, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants