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

Starting via minikube gives the following error: #182

Closed
ridoo opened this issue Jun 20, 2024 · 1 comment
Closed

Starting via minikube gives the following error: #182

ridoo opened this issue Jun 20, 2024 · 1 comment

Comments

@ridoo
Copy link
Contributor

ridoo commented Jun 20, 2024

Starting main branch via minikube gives the following error:

minikube kubectl -- -n geonode logs -f pod/geonode-nginx-86b679cf75-hhns5
/docker-entrypoint.sh: /docker-entrypoint.d/ is not empty, will attempt to perform configuration
/docker-entrypoint.sh: Looking for shell scripts in /docker-entrypoint.d/
/docker-entrypoint.sh: Launching /docker-entrypoint.d/10-listen-on-ipv6-by-default.sh
10-listen-on-ipv6-by-default.sh: info: /etc/nginx/conf.d/default.conf is not a file or does not exist
/docker-entrypoint.sh: Sourcing /docker-entrypoint.d/15-local-resolvers.envsh
/docker-entrypoint.sh: Launching /docker-entrypoint.d/20-envsubst-on-templates.sh
/docker-entrypoint.sh: Launching /docker-entrypoint.d/30-tune-worker-processes.sh
/docker-entrypoint.sh: Configuration complete; ready for start up
2024/06/20 09:46:07 [emerg] 1#1: host not found in upstream "geonode-geoserver" in /etc/nginx/conf.d/geonode.conf:54
nginx: [emerg] host not found in upstream "geonode-geoserver" in /etc/nginx/conf.d/geonode.conf:54

Kubernetes and Minikube versions:

k version --short
Flag --short has been deprecated, and will be removed in the future. The --short output will become the default.
Client Version: v1.27.4
Kustomize Version: v5.0.1
Server Version: v1.30.0

I could successfully start minikube with Kubernetes version v1.27.13.

Originally posted by @ridoo in #181 (comment)

@ridoo
Copy link
Contributor Author

ridoo commented Jun 20, 2024

After testing through K8S versions 1.27 to 1.30 the error was not reproducible anymore for me. 🤷‍♂️

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

1 participant