commit
f52e385e3c
|
@ -19,7 +19,7 @@ The Docker driver allows you to install Kubernetes into an existing Docker insta
|
||||||
|
|
||||||
## Known Issues
|
## Known Issues
|
||||||
|
|
||||||
- Docker driver is not supported on non-amd64 architectures such as arm yet. For non-amd64 archs please use [other drivers]({{< ref "/docs/drivers/" >}}
|
- Docker driver is not supported on non-amd64 architectures such as arm yet. For non-amd64 archs please use [other drivers]({{< ref "/docs/drivers/_index.md" >}})
|
||||||
|
|
||||||
- On macOS, containers might get hung and require a restart of Docker for Desktop. See [docker/for-mac#1835](https://github.com/docker/for-mac/issues/1835)
|
- On macOS, containers might get hung and require a restart of Docker for Desktop. See [docker/for-mac#1835](https://github.com/docker/for-mac/issues/1835)
|
||||||
|
|
||||||
|
@ -29,12 +29,11 @@ The Docker driver allows you to install Kubernetes into an existing Docker insta
|
||||||
|
|
||||||
`sudo mkdir /sys/fs/cgroup/systemd && sudo mount -t cgroup -o none,name=systemd cgroup /sys/fs/cgroup/systemd`.
|
`sudo mkdir /sys/fs/cgroup/systemd && sudo mount -t cgroup -o none,name=systemd cgroup /sys/fs/cgroup/systemd`.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## Troubleshooting
|
## Troubleshooting
|
||||||
|
|
||||||
[comment]: <> (this title is used in the docs links, don't change)
|
[comment]: <> (this title is used in the docs links, don't change)
|
||||||
### Verify Docker container type is Linux
|
### Verify Docker container type is Linux
|
||||||
|
|
||||||
- On Windows, make sure Docker Desktop's container type setting is Linux and not windows. see docker docs on [switching container type](https://docs.docker.com/docker-for-windows/#switch-between-windows-and-linux-containers).
|
- On Windows, make sure Docker Desktop's container type setting is Linux and not windows. see docker docs on [switching container type](https://docs.docker.com/docker-for-windows/#switch-between-windows-and-linux-containers).
|
||||||
You can verify your Docker container type by running:
|
You can verify your Docker container type by running:
|
||||||
```shell
|
```shell
|
||||||
|
@ -42,11 +41,12 @@ You can verify your Docker container type by running:
|
||||||
```
|
```
|
||||||
|
|
||||||
### Run with logs
|
### Run with logs
|
||||||
|
|
||||||
- Run `--alsologtostderr -v=1` for extra debugging information
|
- Run `--alsologtostderr -v=1` for extra debugging information
|
||||||
|
|
||||||
### Deploying MySql on a linux with AppArmor
|
### Deploying MySql on a linux with AppArmor
|
||||||
|
|
||||||
- On Linux, if you want to run MySQL pod, you need to disable AppArmor for mysql profile
|
- On Linux, if you want to run MySQL pod, you need to disable AppArmor for mysql profile
|
||||||
|
|
||||||
If your docker has [AppArmor](https://wiki.ubuntu.com/AppArmor) enabled, running mysql in privileged mode with docker driver will have the issue [#7401](https://github.com/kubernetes/minikube/issues/7401).
|
If your docker has [AppArmor](https://wiki.ubuntu.com/AppArmor) enabled, running mysql in privileged mode with docker driver will have the issue [#7401](https://github.com/kubernetes/minikube/issues/7401).
|
||||||
There is a workaround - see [moby/moby#7512](https://github.com/moby/moby/issues/7512#issuecomment-61787845).
|
There is a workaround - see [moby/moby#7512](https://github.com/moby/moby/issues/7512#issuecomment-61787845).
|
||||||
|
|
||||||
|
|
|
@ -27,4 +27,5 @@ minikube start --driver=podman --container-runtime=cri-o
|
||||||
{{% readfile file="/docs/drivers/includes/podman_usage.inc" %}}
|
{{% readfile file="/docs/drivers/includes/podman_usage.inc" %}}
|
||||||
|
|
||||||
## Known Issues
|
## Known Issues
|
||||||
- Podman driver is not supported on non-amd64 architectures such as arm yet. For non-amd64 archs please use [other drivers]({{< ref "/docs/drivers/" >}}
|
|
||||||
|
- Podman driver is not supported on non-amd64 architectures such as arm yet. For non-amd64 archs please use [other drivers]({{< ref "/docs/drivers/_index.md" >}})
|
||||||
|
|
Loading…
Reference in New Issue