failed to register layer: operation not supported when building Docker image with vmwarefusion driver

[jrutley]

Minikube version (use minikube version): v0.21.0

Environment:

• OS (e.g. from /etc/os-release): Mac OS X Sierra (10.12.5)

• VM Driver (e.g. cat ~/.minikube/machines/minikube/config.json | grep DriverName): vmwarefusion

• ISO version (e.g. cat ~/.minikube/machines/minikube/config.json | grep -i ISO or minikube ssh cat /etc/VERSION): I tried both minikube-v1.0.6.iso and minikube-v0.23.0.iso

• Install tools:
  brew install kubectl

• Others:
  VMWare Fusion 8.5.8
  a hello world Node app

What happened:
I essentially started following the directions from here:
https://kubernetes.io/docs/tutorials/stateless-application/hello-minikube/

with the exception that I substituted vmwarefusion for xhyve

What you expected to happen:
I expected the Docker image to be built successfully

How to reproduce it (as minimally and precisely as possible):

I ran the following commands:
minikube start --vm-driver=vmwarefusion
eval $(minikube docker-env) to set the Docker env
docker build -t hello-node:v1 .

Anything else do we need to know:
My Dockerfile used Node 8 instead of 6.9.2, but I tried with both and got the same result.

Here's what the result looked like:
Jeramys-MBP:kubetest jeramy$ docker build -t hello-node:v1 .
Sending build context to Docker daemon 3.072kB
Step 1 : FROM node:8
8: Pulling from library/node
ad74af05f5a2: Pull complete
2b032b8bbe8b: Extracting [==================================================>] 19.26MB/19.26MB
a9a5b35f6ead: Download complete
3245b5a1c52c: Download complete
afa075743392: Download complete
9fb9f21641cd: Download complete
b1074d048a61: Download complete
602b2c2b7041: Download complete
failed to register layer: operation not supported

Building the Docker image without running eval $(minikube docker-env) builds the image just fine.
I noticed when I opened the Minikube VM directly in VMWare Fusion that it said I should upgrade it to a later image.
Afterward, I downloaded xhyve and it created the image fine

[rvowles]

this seems to be the same issue i am getting, someone here mentioned it: #1087

[jrutley]

Yeah, I saw that issue too. I wasn't sure if it was exactly the same or not, so I opened a new one

[rvowles]

Seems to be, I was able to successfully start it up with the testing url. These are my current instructions to others on my team: minikube config set memory 4096 minikube config set vm-driver vmwarefusion minikube config set kubernetes-version v1.7.0 # next one if you have any difficulty starting, getting kubernetes to actually get past ContainerCreating minikube config set iso-url https://storage.googleapis.com/minikube-builds/1542/minikube-testing.iso minikube start minikube ssh -- sudo cp $HOME/.minikube/machines/minikube/userdata.tar /mnt/sda1/var/lib/boot2docker/ kubectl get pods --all-namespaces

…

On Mon, Jul 31, 2017 at 2:05 PM, Jeramy Rutley ***@***.***> wrote: Yeah, I saw that issue too. I wasn't sure if it was exactly the same or not, so I opened a new one — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#1764 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AADZ2D6_3Z3ASUqT4WS7YJki3UbX9APJks5sTTZ8gaJpZM4Ol1PY> .

-- --- Richard Vowles, Groovy, Java, Javascript, AngularJS - Contract Software for Hire! ph: +64275467747, web: www.google.com/+RichardVowles

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

[jrutley]

It's a bit late, but it seems to be fixed