-
Notifications
You must be signed in to change notification settings - Fork 271
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
Windows Containers side by side with Rancher Desktop - for windows containers implementation ideas #3999
Comments
@the-mentor there is a small typo in step 3. e) it should be:
Working well otherwise, thanks! |
@the-mentor Thank your instructions, it makes sense but I have a question for you regarding that part:
According to Moby's documentation it seems that building docker requires to have a docker that runs on Windows... If I am right it means that Docker Desktop is required no matter what to build Moby. Here is the documentation I am referring to:
Is that correct? Or could you take a moment to explain how you were able to compile Moby on Windows? |
@Alexandre-Georges a few things have changed since I wrote the guide. I hope that helps |
@the-mentor you could update your original post and replace your first step I would like to also point out on the microsoft documentation Prep Windows for containers that links to a script install-docker-ce.ps1 which does step 1, 2 and most of step 3. |
When I run this locally, using the install-docker-ce.ps1 script or the above doc I typically encounter this error when I run the Server: Any help in getting past this would be much appreciated. I have WSL2 enabled, features: Containers, HyperV, and using binary: docker-24.0.6 |
For info, the script install-docker-ce.ps1 is meant to be run in the default version of powershell for your Windows. Do not use the latest versions of powershell, it won't work.
Make sure that your file {
'group' = 'docker-users',
} If yes, you can check that your user is in the local group : Get-LocalGroup -Name docker-users # this should print a line "docker-users"
Get-LocalGroupMember -Name docker-users # this should print a line with your current user If there are no local group named "docker-users" add it: New-LocalGroup -Name docker-users -Description 'Docker engine users'
# Then add your user to the group:
Add-LocalGroupMember -Name docker-users -Member $Env:UserName Then try restarting your computer. |
if you get the Error: hcs::CreateComputeSystem : The container operating system does not match the host operating system. |
Run
Not |
Problem Description
Hi,
After talking with Jan on slack here is my documentation on how how I got moby (open source docker) and rancher desktop to install and work side by side on my windows workstation.
Enable-WindowsOptionalFeature -Online -FeatureName containers –All
a) Copying it to
c:\program files\docker\dockerd.exe
b) Registering it as a service using the following commands:
cd c:\program files\docker
anddockerd.exe --register-service
c) Creating the security group and
C:\ProgramData\docker\config\daemon.json
file using the below PowerShell codethis will create a security group called
docker-users
and all members of this group wont need admin privileges to interact with the docker daemon.d) Start the docker engine service via UI or PowerShell
Start-Service docker
e) The last step would be to create a docker context using the docker cli
docker context create docker-windows --description "docker windows engine" --docker "host=npipe:////./pipe/dockerWindowsEngine"
then once everything is configured we can switch to the windows context using
docker context use docker-windows
.running
docker system info
will show we're running windows containerswe can always switch back to use rancher by running
docker context use default
Let me know if this is enough information or if you need anything else
Proposed Solution
Add support for windows containers via moby (open source docker) as outlined above and add support in the rancher-desktop UI.
Additional Information
No response
The text was updated successfully, but these errors were encountered: