Open jay7x opened 3 years ago
This seems like a duplicate of #329.
Also, I wonder if it's related to the following:
I wonder if there's a way for dgoss to detect this.
Ah, you're right! #329 is about the same issue. And from second link it seems the actual reason is not the private /tmp but how docker hyperkit VM is started. Well, that's explains.
You can close this then. #329 is enough and there is cp
strategy which should work. Thank you!
Regarding way to detect.. You can try to check the goss presence (or execution result) with mount
strategy and if there is no fallback to cp
strategy.
I'll keep this ticket open to implement the detection. I think it should error and fail and allow the user to decide to use cp
, only because docker_output.log doesn't show up in cp
mode, so it's not exactly the same user experience.
Thanks!
Describe the bug It seems
dgoss
doesn't work on MacOS because/tmp
is private (I guess). I.e. docker cannot see files created by user.How To Reproduce Install current dgoss & goss on MacOS as described in documentation and try
dgoss edit alpine sleep 1000
e.g. You may see there is nogoss
binary copied into container. See Actual Behavior for example.Expected Behavior It's expected to have
/goss/goss
binary in docker container.Actual Behavior
Environment:
How to fix I fixed it for myself by applying the following change. Actually I'm just using
~/tmp
instead of/tmp
. I'm not sure it's good solution for everyone though.. I'd prefer to be able to override it via environment variable.