You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In response to #297, we're seeing this issue as well, with two differences. One, the command is passed in via our config.hcl file.
exec {
command = "java -jar app.jar"
}
Secondly (and perhaps the actual cause?) is we're shipping our applications in distroless containers (which don't contain shells by default). We can migrate to using the command array-based syntax, but we just want to make sure this isn't a known regression/breaking change.
Envconsul version
envconsul v0.13.2 (dd416ce)
Configuration
consul {
address="127.0.0.1:8500"
}
exec {
command="java -jar /data/bin/app-release-995.jar"
}
prefix {
# This tells Envconsul to use a custom formatter when printing the key. The# value between `{{ key }}` will be replaced with the key.format="custom_{{ key }}"path="foo/bar"
}
In response to #297, we're seeing this issue as well, with two differences. One, the command is passed in via our
config.hcl
file.Secondly (and perhaps the actual cause?) is we're shipping our applications in distroless containers (which don't contain shells by default). We can migrate to using the command array-based syntax, but we just want to make sure this isn't a known regression/breaking change.
Envconsul version
Configuration
Command
Debug output
Expected behavior
envconsul should run with existing behavior.
Actual behavior
Error with
2023-06-08T21:23:38.045Z [ERROR] envconsul: parsing command: executable file not found in $PATH
Steps to reproduce
2023-06-08T21:23:38.045Z [ERROR] envconsul: parsing command: executable file not found in $PATH
References
Similar issue
The text was updated successfully, but these errors were encountered: