Issues Starting Containers After Linux Kernel Update
Asked by
CuriousCoder92
I updated my server last night, and since then I've been encountering errors in many containers that were working fine before. I'm seeing messages like `sysctl: error setting key 'net.ipv4.conf.all.src_valid_mark': Read-only file system`. I'm trying to configure the following settings:
cap_add:
- NET_ADMIN
- SYS_MODULE
sysctls:
- net.ipv4.ip_forward=1
- net.ipv4.conf.all.src_valid_mark=1
Could the kernel upgrade have caused something to break, or was something drastically changed? I'm running Ubuntu 24.04 LTS with the kernel version 6.8.0-87-generic, and Docker is at version 28.5.1, build e180ab8.
Answers
If everything else fails, a quick troubleshooting step is to boot with the previous kernel version and see if that resolves the issue. Just be careful, since switching kernels might mess with your existing dependencies.
Reply to this answer
It sounds like you're hitting permission issues, especially since you're getting that 'read-only file system' error. Check to ensure your container isn't running in a virtualized environment like WSL or Mac, because that could be causing the issue. You might also want to try launching the container with the `--privileged` flag to see if that allows it to change kernel parameters.
Reply to this answer
Add your answer
Answers are reviewed before publication.
Related Discussions