-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Running inside Kubernetes #373
Comments
I have zero experience with Kubernetes, so hopefully another user who knows how to do it can help you. |
Or maybe this pull-request: https://github.com/dockur/windows/pull/304/files |
you can substitute --cap-add NET_ADMIN to --privileged but it s insecure. There isn't any workaround for the moment, other than that. Got a problem on my kubernetes : qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000007H:EDX.invtsc [bit 8] so best luck to youuuu as well ^^ |
@thomasblot1 That error is when your CPU doesnt support flags for Hyper-V, you can add the environment variable: |
I have now added an example Kubernetes manifest, see: https://github.com/dockur/windows/blob/master/kubernetes.yml |
Is it possible to run it in a cluster Kubernetes?
I got this error when I tried:
❯ Starting Windows for Docker v2.10...
❯ For support visit https://github.com/dockur/windows
RTNETLINK answers: File exists
❯ ERROR: Failed to create bridge. Please add the following setting to your container: --cap-add NET_ADMIN
Spec:
The text was updated successfully, but these errors were encountered: