Abe Music

:+1: I too would like to pile on this issue. For the time being I will be looking into using the workaround above (thanks for providing that @thesociable)

+1 as well. I commented on PR #1155 mentioned above. Trying to find any workaround that doesn't result in a poor experience for the user. Ideas anyone? https://github.com/aws-amplify/aws-sdk-ios/pull/1155#issuecomment-618123577

I went a similar direction but send the refresh token so the user doesn’t need to open the app once per hour. Probably not the best way, but it works

Also, using the pxe command line we can take advantage of what appears to be some sort of caching in pixiecore's /_/ipxe endpoint by doing: ``` autoboot ... this will...

Thanks for the speedy reply :) Apologies for not getting back to you sooner. I've pulled latest and unfortunately the timings aren't present in the log I'm seeing until I...

I've also made a screen capture of the proxmox boot along with two shells with the logs for pixiecore and the API server if that would be helpful. It shows...

I just ran a tcpdump to catch what's going on during a pxe `autoboot` that fails and noticed that a DHCP Offer with the boot filename to pixiecore's ipxe endpoint...

I'll take a look at your recent commit and build the image to test in our environment. For completeness, here's a screenshot of the wireshark stream: http://imgur.com/a/te44X > What container...

Here's an updated log with the automated net boot that's timing out due to the DNS and using the latest pixiecore container: ``` 2017/03/03 16:11:24 [Init] Starting Pixiecore goroutines 2017/03/03...

We've updated our workflow to override the pixiecore container's /etc/resolv.conf with just 127.0.0.1 as a nameserver. It works every time...we would love to be able to figure it out without...