Lachlan Donald

This basically brings things up to parity with lifecycle hooks on EC2, so I'd say this pretty much addresses my original issue. Happy to close this out, thanks for your...

I have an M1 MacBook Air if I can be of help with testing @ysmood!

On the latest master (ad95d98dc1d87f955e1a0e10121b294a2349dfd4) I built with the following: ``` $ uname -a Darwin Alexandra 20.3.0 Darwin Kernel Version 20.3.0: Thu Jan 21 00:06:51 PST 2021; root:xnu-7195.81.3~1/RELEASE_ARM64_T8101 arm64 $...

I thought it was odd that the builder didn't use the tag I specified, but I must have been misreading the output of `buildx`. The command as you mentioned above...

``` ~/temp/ › touch XD ~/temp/ › [D] notify.Create|notify.FSEventsIsFile (/Users/lachlan/temp/XD, i=0, ID=51566809, len=1) [D] split()=notify.Create|notify.FSEventsIsFile [D] 51566809: single event: notify.Create [D] dispatching notify.Create on "/Users/lachlan/temp/XD" 2015/05/22 16:09:11 received notify.Create: "/Users/lachlan/temp/XD"...

Mind blown. https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_version.html > To use all of the available policy features, include the following Version element before the Statement element in all of your policies. So terrible.

This issue makes testing and debugging really difficult. It seems like there are lots of places where `\Exception` is caught. Perhaps a pluggable exception handler would be a good way...

We're seeing this problem too.

Might I suggest changing this issue title to `Mounting unix sockets doesn't work with Sysbox in auto userns ID mapping mode`? This issue is much broader than than just mounting...

We've really tried to avoid supporting forks, but I hear you. I think I'd be ok with making this a packer variable though.