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

unregister_netdevice kernel message after restarting container #205

Closed
ivanjx opened this issue Aug 13, 2022 · 5 comments
Closed

unregister_netdevice kernel message after restarting container #205

ivanjx opened this issue Aug 13, 2022 · 5 comments

Comments

@ivanjx
Copy link

ivanjx commented Aug 13, 2022

linuxserver.io

im getting a lot of this kernel messages on my ssh terminal that says:

Message from syslogd@home-server at Aug 13 15:06:36 ...
 kernel:[614037.260262] unregister_netdevice: waiting for lo to become free. Usage count = 1

that happens everytime i restarted the transmission container. the message will only go away if i reboot the docker host. here is my docker daemon config:

{
    "dns": ["8.8.8.8", "8.8.4.4"],
    "ipv6": true,
    "experimental": true,
    "ip6tables": true,
    "fixed-cidr-v6": "fd00::/80"
}

Expected Behavior

no kernel messages after rebooting container

Current Behavior

giving a lot of kernel messages described above

Steps to Reproduce

  1. run the container
  2. reboot the container using docker restart command

Environment

OS: Ubuntu 20.04
CPU architecture: arm64
How docker service was installed:

official docker website guide

Command used to create docker container (run/create/compose/screenshot)

transmission:
    image: xxxx
    restart: always
    ports:
        - 51413:51413/tcp
        - 51413:51413/udp
    environment:
        PUID: "1000"
        PGID: "1002"
        USER: "x"
        PASS: "x"
    volumes:
        - /data/x1:/config
        - /data/x2:/share

Docker logs

@project-bot project-bot bot added this to To do in Issue & PR Tracker Aug 13, 2022
@github-actions
Copy link

Thanks for opening your first issue here! Be sure to follow the bug or feature issue templates!

@j0nnymoe
Copy link
Member

Why have you blanked out the image name? For all we know you might not be using our container.

@ivanjx
Copy link
Author

ivanjx commented Aug 13, 2022

doesnt really matter but here you go: https://gitlab.com/ivanjx/transmission-flood/-/blob/master/Dockerfile

@j0nnymoe
Copy link
Member

quick google shows that error is not related to our container but likely due to your changes in the daemon.json
moby/moby#5618

@aptalca
Copy link
Member

aptalca commented Aug 13, 2022

This section is for bug reports about our image, not general docker support. Closing.

@aptalca aptalca closed this as completed Aug 13, 2022
Issue & PR Tracker automation moved this from To do to Done Aug 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

3 participants