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

Logs command fails with "no such file or directory" if a given K8s service hasn't been staged to the build dir #3900

Closed
eysi09 opened this issue Mar 7, 2023 · 2 comments

Comments

@eysi09
Copy link
Collaborator

eysi09 commented Mar 7, 2023

Bug

Current Behavior

If a given service belongs to a K8s module and it hasn't been built and thereby is not in the .garden/build directory, the garden logs command will fail with:

ENOENT: no such file or directory, open '/path/to/.garden/build/my-servicre/my-service.yml'

Reproducible example

  1. Change into the kubernetes-module example project.
  2. Run rm -rf ./.garden/build
  3. Run garden logs.

Workaround

Run garden build or garden deploy before running the logs command.

Suggested solution(s)

Either we read the manifest required to find the logs from the src dir or ensure that we stage it before getting the logs.

Your environment

Only tested on Garden 0.12 but AFAICT is broken on 0.13 as well.

@Walther
Copy link
Contributor

Walther commented Jun 5, 2023

potentially related #4516 ?

@10ko
Copy link
Member

10ko commented Feb 8, 2024

This should be fixed, please re-open if that's not the case.

@10ko 10ko closed this as completed Feb 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants