Closed michaelwittig closed 6 years ago
Hi @michaelwittig /sbin is a path which only gets set for the root user $PATH env, there is a new use_sudo option, this should make it work and actually some tests require escalated privileges depending on what is being tested, setting the use_sudo flag to true may be of help here.
thanks @vamegh
use_sudo
is working
{
"provisioners": [
...
{
"type": "goss",
"use_sudo": true,
"tests": [
"./build/goss.yaml"
]
}
]
}
Hi,
I use the goss provisioner with the following config:
./packer.json
./build/goss.yaml
The goss binary seems to be started with a PATH that does not contain
sbin
. On the target system:packer output:
I could not figure out where PATH is actually used and where it comes from since this is a remote command. Any hints how to debug this issue?