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

Carrier never gets ready #604

Closed
SteinRobert opened this issue May 8, 2024 · 0 comments · Fixed by #605
Closed

Carrier never gets ready #604

SteinRobert opened this issue May 8, 2024 · 0 comments · Fixed by #605
Labels
bug 🐛 Something isn't working

Comments

@SteinRobert
Copy link
Contributor

What happened?

I bridged a workload and the pod never gets ready.

What did you expect to happen?

The pod to get ready.

Please provide the output of gefyra check.

.

How can we reproduce it (as minimally and precisely as possible)?

.

What Kubernetes setup are you working with?

$ kubectl version
# paste output here

OS version

# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here

Anything else we need to know?

Problem is, that nginx cannot create certain directories. Some cache paths need to be reconfigured.

@SteinRobert SteinRobert added the bug 🐛 Something isn't working label May 8, 2024
SteinRobert added a commit that referenced this issue May 8, 2024
fix(#604): set cache dirs for carrier nginx
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.

1 participant