@Eli, I tested kub with atomic-5 and it can start docker instances without any problems and I can attach for them.
But busybox cannot start correctly docker run -it busybox Post http:///var/run/docker.sock/v1.19/containers/b350ac5a0823a69207792d813e157c2b1b56d608eebefcfc0ea5995c6146e0c4/start: EOF. Are you trying to connect to a TLS-enabled daemon without TLS?
But instance is actually running docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES b350ac5a0823 busybox "sh" 8 seconds ago Up 7 seconds insane_rosalind
And I can attach to it docker exec -i -t b350ac5a0823 /bin/sh
@Eli, I tested kub with atomic-5 and it can start docker instances without any problems and I can attach for them.
But busybox cannot start correctly /var/run/ docker. sock/v1. 19/containers/ b350ac5a0823a69 207792d813e157c 2b1b56d608eebef cfc0ea5995c6146 e0c4/start: EOF. Are you trying to connect to a TLS-enabled daemon without TLS?
docker run -it busybox
Post http://
But instance is actually running
docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
b350ac5a0823 busybox "sh" 8 seconds ago Up 7 seconds insane_rosalind
And I can attach to it
docker exec -i -t b350ac5a0823 /bin/sh