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

Remove tun/tap from the default device rules #3468

Merged
merged 1 commit into from
May 10, 2022

Commits on May 4, 2022

  1. Remove tun/tap from the default device rules

    Looking through git blame, this was added by commit 9fac183
    aka "Initial commit of runc binary", most probably by mistake.
    
    Obviously, a container should not have access to tun/tap device, unless
    it is explicitly specified in configuration.
    
    Now, removing this might create a compatibility issue, but I see no
    other choice.
    
    Aside from the obvious misconfiguration, this should also fix the
    annoying
    
    > Apr 26 03:46:56 foo.bar systemd[1]: Couldn't stat device /dev/char/10:200: No such file or directory
    
    messages from systemd on every container start, when runc uses systemd
    cgroup driver, and the system runs an old (< v240) version of systemd
    (the message was presumably eliminated by [1]).
    
    [1] systemd/systemd@d5aecba
    
    Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
    kolyshkin committed May 4, 2022
    Configuration menu
    Copy the full SHA
    2ce40b6 View commit details
    Browse the repository at this point in the history