samples/guestbook: terraform apply fails on AWS about go-cloud HOT 6 CLOSED

That would work too, but I'd like to preserve the user's temporary directory preferences when possible.

from go-cloud.

I've never seen that before, and seems like a Docker setup issue? Happy to help debug, but I don't know what to do.

from go-cloud.

This might also be a Mac OS X issue, which is going to be difficult to debug without a Mac on hand.

I am wondering if we should not order one for investigating this exact sort of thing. We are going to need to be confident that things work on it.

from go-cloud.

The fix is easy enough. I just need to configure my vanilla docker to support mount points inside the /var directory. My point is this adds an additional step for users who might not know what that error means.

One solution would be to create a temp directory next to the provision-db.sh script instead.

from go-cloud.

Based on the documentation, default Docker settings allow for /private and /tmp to be used. IIRC /var/folders/... is actually usually a symlink under /private or some such silliness. Perhaps if I evaluated symlinks in the script, this would clear up the issue? @enocom, I'll send you a PR which would test this hypothesis, but if it doesn't work, then I'll need to get my hands on a Mac.

from go-cloud.

Yes. /var is symlinked to/private/var. Why not just put the temp dir in the working directory and add a line to the .gitignore?

from go-cloud.