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

stale sys-devices-virtual-net-veth... devices in systemctl list-units after every docker run #2313

Open
Ferengee opened this Issue Jan 10, 2018 · 1 comment

Comments

Projects
None yet
3 participants
@Ferengee

Ferengee commented Jan 10, 2018

Issue Report

Bug

Container Linux Version

NAME="Container Linux by CoreOS"
ID=coreos
VERSION=1576.5.0
VERSION_ID=1576.5.0
BUILD_ID=2018-01-05-1121
PRETTY_NAME="Container Linux by CoreOS 1576.5.0 (Ladybug)"
ANSI_COLOR="38;5;75"
HOME_URL="https://coreos.com/"
BUG_REPORT_URL="https://issues.coreos.com"
COREOS_BOARD="amd64-usr"

Environment

Bare metal install (https://coreos.com/os/docs/latest/installing-to-disk.html)
coreos-install -d /dev/sda

  • on xen as a virtual machine
  • on 3x Dell R610 with a 3 machine cluster

Expected Behavior

Every virtual network device reported by systemctl list-units is actually there.

Actual Behavior

Every time I start a docker container systemctl list-units reports 2 virtual ethernet devices instead of one.
ip addr show shows one active
the sys-devices-virtual-net-vethxxx.device unit entries build up over time (for every container start one extra).

Reproduction Steps

  1. install coreos using barebone install
  2. check with docker ps that there are no containers running
  3. check network interfaces using ip and systemctl
# systemctl list-units | grep sys-devices-virtual-net-veth |wc -l
>       0
# ip addr show | grep sys-devices-virtual-net-veth  |wc -l
>       0
  1. start a docker container
# docker run -ti ubuntu /bin/bash
...
  1. check network interfaces again
# systemctl list-units | grep sys-devices-virtual-net-veth |wc -l
>       2
# ip addr show | grep veth |sys-devices-virtual-net-veth -l
>       1
@r7vme

This comment has been minimized.

Show comment
Hide comment
@r7vme

r7vme Apr 12, 2018

This can be duplicate of systemd/systemd#7370 , which is fixed for automount and swap units, but not for device and slice units.

Workaound for us was to do systemctl daemon-reload.

r7vme commented Apr 12, 2018

This can be duplicate of systemd/systemd#7370 , which is fixed for automount and swap units, but not for device and slice units.

Workaound for us was to do systemctl daemon-reload.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment