Kaniko should only be run inside of a container

[VF-mbrauer]

After applying your kaniko-demo with minikube version: v1.25.2 I am getting after running the kaniko-git.yaml this error:

Enumerating objects: 196, done.
Counting objects: 100% (196/196), done.
Compressing objects: 100% (156/156), done.
Total 196 (delta 38), reused 191 (delta 33), pack-reused 0
kaniko should only be run inside of a container, run with the --force flag if you are sure you want to continue

Resulting in

NAME     READY   STATUS   RESTARTS   AGE
kaniko   0/1     Error    0          2m55s

[VF-mbrauer]

So, after adding the additional argument --force it is working.
It still gives me the WARNING

WARN[0000] kaniko is being run outside of a container. This can have dangerous effects on your system

but at least it works.
Just wondering if that has to do with the latest Kubernetes version or the latest image of Kaniko?
And why does it say Running outside of a container, because it isn't, it runs inside??

[vfarcic]

That's strange. I just created a Minikube cluster based on v1.25.2 (just as yours) and went through all the commands https://gist.github.com/627fcfbfbc17a683a70210947e02eaa3. It worked from the get-go and --force was not mentioned anywhere in the logs. The only thing that comes to my mind is that there might be differences in how minikube creates a cluster depending on the virtualization you chose. I'm running it with VirtualBox? If you can let me know what you're using for virtualization, I can try to reproduce it again.

[VF-mbrauer]

I am using macOS. Minikube runs in a docker environment. So, the usual macOS Minikube installation as it comes from the Kubernetes webpage. I did not touch the standard configuration.

Just let me know if you need anything else.
Thanks.

[vfarcic]

I just reproduced it by using Docker as a Minikube driver (I used VirtualBox before). I still do not know why that is happening but, at least, now we know that it's related to Docker or, to be more precise, when a Kubernetes cluster is running inside a container (Minikube with docker driver is actually k8s inside a container). I suspect that the same issue would happen with KinD.

Unfortunately, I can't say much more since I'm not using Docker or Minikube myself. I switched to Rancher Desktop a while ago and set those two up (Minikube and Docker) for this issue inside a laptop that is hardly working anymore.

[tt5]

microk8s:

[...]
spec:
  containers:
  - name: kaniko
    env:
      - name: container
        value: 'docker'
[...]