for-win
for-win copied to clipboard
docker
Host Networking: could not get the cgroupv2 ID for /sys/fs/cgroup/docker
Description
network host failed to enable, login is not working and docker seems stop working from nowhere. again.
Reproduce
just open docker to rain errors, like "Host Networking could not be started: could not get the cgroupv2 ID for /sys/fs/cgroup/docker: no such file or directory"
Expected behavior
run fine
docker version
latest
docker info
info
Diagnostics ID
6hjk541564165
Additional Info
No response
@gustavozantut Could you generate a diagnostic and update your original message to put the diag ID in there please? See here: https://docs.docker.com/desktop/troubleshoot/#diagnose-from-the-terminal
This would help us understand what's going on. I think could not get the cgroupv2 ID for /sys/fs/cgroup/docker: no such file or directory might be a red herring, and the Engine might fail to start properly.
And for anyone else facing the same issue / error message, could you provide a diag ID also please?
@gustavozantut Could you generate a diagnostic and update your original message to put the diag ID in there please? See here: https://docs.docker.com/desktop/troubleshoot/#diagnose-from-the-terminal
This would help us understand what's going on. I think
could not get the cgroupv2 ID for /sys/fs/cgroup/docker: no such file or directorymight be a red herring, and the Engine might fail to start properly.And for anyone else facing the same issue / error message, could you provide a diag ID also please?
@akerouanton done!
[2024-11-05T15:26:00.379040300Z][com.docker.diagnose.exe.public] using HTTP proxy inside com.docker.backend
Uploaded diagnostics to: https://docker-pinata-support.s3.amazonaws.com/incoming/3/CC172A87-C209-466E-9F10-EB7DB9B9FDE4/20241105152515.zip
Diagnostics ID: CC172A87-C209-466E-9F10-EB7DB9B9FDE4/20241105152515 (uploaded)```
Apparently when I updated to 3.34.3 didn't go well, after update it continues to show older version.reinstalling made it work but lost some things
@akerouanton Here it is:
C9336CE4-8D76-45F5-A509-B428CD159D8D/20241105172325
@laithalsaadoon @MedAymenF Thanks! In both cases, I see that we're looking for /sys/fs/cgroup/docker, whereas the engine uses /sys/fs/cgroup/01-docker, although I'm not entirely sure why. I see that both of you have set cgroup_no_v1=all, maybe that's the reason 🤔
Same issue here.
@akerouanton: Diagnostics ID: 3C74442D-AFBA-4A81-A402-599C6A6F012A/20241106125511 (uploaded)
@akerouanton same issue here
Diagnostics ID: 58974BE7-6033-44AA-8F0E-AEE0B684B455/20241107163136 (uploaded)
and I just "factory reset" my docker desktop
uninstalling docker desktop and rolling back to docker desktop 4.34.3 allows me to login and enable host networking again
uninstalling docker desktop and rolling back to docker desktop 4.34.3 allows me to login and enable host networking again
yes but doing it every update because people can't test before release is a little boring
Thanks all for your diags. A fix was merged a few days ago, and the next release due really soon will include it.
Thanks all for your diags. A fix was merged a few days ago, and the next release due really soon will include it.
Nice, thank you. I'm glad to know that next update when i cold reinstall docker again because of new update errors this one will be fixed
Thanks all for your diags. A fix was merged a few days ago, and the next release due really soon will include it.
Why u changed name of the issue? it's incorrect to state that you release without proper testing? seems not
Thanks all for your diags. A fix was merged a few days ago, and the next release due really soon will include it.
Would you know which release will include that fix @akerouanton, unfortunately 4.36 didn't seem to fix it I still see this error and login doesn't really work properly.
I forgot to mention that I rolled back to 4.34.1 and the issues are gone, login works fine and not error message about host networking.
anyone already updated? everything ok or i'll have to build all my images all over again?
For me updating did fix the issue, on multiple windows installations.
To which version @fverdoja and OS version? I tried with 4.36.0 and it didn't fix the issue for me. Windows 11 24H2.
I can confirm also, it's working fine for me also now on docker dekstop 4.36.0 in Windows 11 24H2.
Not sure what happened before.
I encountered this issue at docker desktop 4.36.0, and I upgrade it to 4.39.0, the issue is still there, not sure what I should do. reinstall?
@b95678 Could you provide a diag please?
Diagnostics ID: 8871A6FF-FDA2-4D30-BDB0-8F633019361D/20250312080319 (uploaded)
same issue at v4.40.0, after I updated it from 4.30.0. Diagnostics ID: 1A417D36-B893-416C-895E-15194FCEA543/20250409125702
it's mesmerizing how docker developers can cultivate bugs for years, eg.: this one and the memory leakage
again... now it wont even generate diag
docker engine does not start, extensions dont load
@gustavozantut that looks like a different issue. The diagnostics generation can take some time depending on the health of your setup. You may also generate one from the terminal: & "C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe" gather -upload
@gustavozantut that looks like a different issue. The diagnostics generation can take some time depending on the health of your setup. You may also generate one from the terminal:
& "C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe" gather -upload
i simply just purge clean reinstall everything all again, getting used to it :)