Skip to content
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

No network connection after upgrade to Kernel 6.8.0-54 #1073

Closed
taylormia opened this issue Mar 1, 2025 · 2 comments
Closed

No network connection after upgrade to Kernel 6.8.0-54 #1073

taylormia opened this issue Mar 1, 2025 · 2 comments

Comments

@taylormia
Copy link

Operating system

Linux Mint 22.1 Kernel 6.8.0-54

Description

After updating Linux Mint 22.1 to Kernel 6.8.0-54, the Win 11 container boots fine but has no network connection. No errors in the boot up log. The host network is working.

Docker compose

services:
windows:
image: dockurr/windows
container_name: windows11
environment:
VERSION: "win11"
DISK_SIZE: "256G"
RAM_SIZE: "16G"
CPU_CORES: "4"
USERNAME: "username"
PASSWORD: "password"
devices:
- /dev/kvm
- /dev/net/tun
cap_add:
- NET_ADMIN
ports:
- 8006:8006
- 3389:3389/tcp
- 3389:3389/udp
stop_grace_period: 2m
volumes:
- /home/user/Documents/windows11-docker:/storage
- /home/user:/shared

Docker log

`Starting Windows for Docker v4.16...
❯ For support visit https://github.com/dockur/windows
❯ CPU: 11th Gen Intel Core i7 11850H | RAM: 54/63 GB | DISK: 1628 GB (ext4) | KERNEL: 6.8.0-54...

❯ Booting Windows using QEMU v9.2.1...

BdsDxe: loading Boot0004 "Windows Boot Manager" from HD(1,GPT,F2144FAC-B9A5-4FD5-8DF1-03CBD23CD0DA,0x800,0x40000)/\EFI\Microsoft\Boot\bootmgfw.efi
BdsDxe: starting Boot0004 "Windows Boot Manager" from HD(1,GPT,F2144FAC-B9A5-4FD5-8DF1-03CBD23CD0DA,0x800,0x40000)/\EFI\Microsoft\Boot\bootmgfw.efi
❯ Windows started succesfully, visit http://localhost:8006/ to view the screen...
`

Screenshots (optional)

No response

@HeInfinity
Copy link

HeInfinity commented Mar 2, 2025

I have the same problem, it says that there is no network and that the driver needs to be installed. But I can't get the driver to install successfully.

I don't know what I did, but it seems to be because of iptables. Just reboot docker.

@taylormia
Copy link
Author

The problem seems to have resolved itself. Bridged networking was not working, so I tried configuring for static or DHCP IP from local LAN by adding macvlan using Portainer - which didn't work for some reason. Deleted the macvlan configuration from Portainer and compose file and restarted with original compose configuration - and voila , bridged networking works again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants