I just upgraded to the Windows 10 Anniversary Update (1607, 2016-08-02) and wanted to try Windows containers.
I followed the most recent guide I could find: Windows
Was in exactly the same situation. However, after upgrading the Docker images, my error changed to a timeout (different from yours).
docker: Error response from daemon: container 219aa480b05d7c7f8110b734dee75e3c2e1a66e230ca066f5e463f0976092476 encountered an error during CreateProcess failed in Win32: The remote procedure call failed. (0x6be) extra info: {"ApplicationName":"","CommandLine":"cmd","WorkingDirectory":"C:\\","Environment":{},"EmulateConsole":true,"CreateStdInPipe":true,"CreateStdOutPipe":true,"CreateStdErrPipe":false,"ConsoleSize":[40,100]}.
I then applied the registry hack that the instructions said was required for a known issue with the technical preview. I'd assumed it was no longer required with the official release, but apparently it is, because I can now connect to the container. Try:
Set-ItemProperty -Path 'HKLM:SOFTWARE\Microsoft\Windows NT\CurrentVersion\Virtualization\Containers' -Name VSmbDisableOplocks -Type DWord -Value 1 -Force