This section could (obviously) use more work. Contributions are most appreciated!
This issue often comes up on Linux, and in other scenarios where the filesystem doesn't support event-based file watching.
Thankfully, you can in most cases avoid this problem using the modules.exclude
field in your project config, and/or the exclude
field in your individual module configs. See the Including/excluding files and directories section in our Configuration Files guide for details.
This is a known issue with Windows and may affect many Node.js applications (and possibly others). To fix it, you can open the Windows Defender Security Center and either
a) disable Real-time protection; or
b) click "Add or remove exclusions" and add "$HOME\.garden" to the list of exclusions.
You need to set tmux to use 256 colors. As per the official documentation, you can do that by adding set -g default-terminal "screen-256color"
or set -g default-terminal "tmux-256color"
to your ~/.tmux.conf
file.
This could be because Garden is scanning the project files. Make sure you exclude things like node_modules
or other large vendor directories. See this section of our docs.
Garden does create the ingress at the Kubernetes level. However, it does not print the ingresses with the CLI output and the Garden command call won't work. This is a known issue.
Pinging the service will still work and you'll see the Ingress resource if you run kubectl get ingress --namespace <my-namspace>
.
This is a well-known Helm issue. You'll need to delete the release manually with helm -n <namespace> uninstall <release-name>
There's an open pull request for a fix.
This is likely because they're being excluded somewhere, e.g. in .gitignore
or .gardenignore
. Garden currently respects .gitignore
but we plan to change that in our next major release.
Make sure to use the outputs
field from the container module being referenced.
For example:
kind: Moduletype: helmname: my-modulevalues:image:# Use the outputs field from the container modulerepository: ${modules.my-module-image.outputs.deployment-image-name}
This may be due the the NFS provisioner not playing well with EKS and AKS.
On EKS, you can use efs
instead, which may be more stable and scalable than the default NFS storage
On AKS, you can use azurefile
.
You'll need to install the provisioners yourself and override the storage.sync.storageClass
field in the kubernetes
provider config.
This can occur if nginx is not able to bind to its default port which is port 80
. Stopping the process that occupies the port should solve the issue.
You can also skip the nginx installation if you already have a separate ingress controller installed, by setting setupIngressController: null
in your local-kubernetes
provider configuration.
If this error came up when running the garden
binary from inside your ~/Downloads
directory, try moving it outside the ~/Downloads
directory before running it again.
If you're still getting this error, a workaround is to find the garden
binary in Finder, CTRL-click it and choose Open. This should prevent this error message from coming up again.
See also: https://support.apple.com/en-gb/guide/mac-help/mh40616/mac
This is a bug in Docker CE (i.e. Docker for Desktop), version 2.4.x.y
. See this GitHub issue comment for a fix and more details.
In some container repositories, you may need to create the cache repo manually.
See this section of our docs and this GitHub comment for more details.