[Touch-packages] [Bug 1810689] Re: HDA Intel PCH / Realtek ALC269VB not seen by pulseaudio (whereas alsa see it) after ubuntu 18.10 upgrade
*** This bug is a duplicate of bug 210472 *** https://bugs.launchpad.net/bugs/210472 Removing timidity did the job. Thanks. ** This bug has been marked a duplicate of bug 210472 Timidity daemon doesn't play nice with pulse audio -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1810689 Title: HDA Intel PCH / Realtek ALC269VB not seen by pulseaudio (whereas alsa see it) after ubuntu 18.10 upgrade Status in pulseaudio package in Ubuntu: Incomplete Bug description: I was using ubuntu 18.04 on my computer (and previously 17.10), and I got the sound card working correctly with pulseaudio. After upgrading to 18.10, pulseaudio interface only detect my usb microphone (BIRO UM1), but it does not detect my computer internal sound card, either for sinking or as a source. I only have a "fictive sink". I have done some experiments: using pacmd, if I try to `load-module module-udev-detect`, nothing happens, and `journalctl --user-unit pulseaudio.service` tells me that the module was already loaded and refuse to load again. If I use `load-module module-detect` the sound card is detected but does not seems to work correctly ! If I use `load-module module-alsa-sink device=default` and `load-module module-alsa-source device=default` my sound card is seens and works as expected. So the problem seems with the module-udev-detect not doing its job correctly (or not having necessary rules ?) My system: $ lsb_release -a LSB Version: core-9.20170808ubuntu1-noarch:printing-9.20170808ubuntu1-noarch:security-9.20170808ubuntu1-noarch Distributor ID: Ubuntu Description: Ubuntu 18.10 Release: 18.10 Codename: cosmic $ uname -a Linux tignasse 4.18.0-13-generic #14-Ubuntu SMP Wed Dec 5 09:04:24 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo lshw ... *-multimedia description: Audio device produit: Sunrise Point-LP HD Audio fabriquant: Intel Corporation identifiant matériel: 1f.3 information bus: pci@:00:1f.3 version: 21 bits: 64 bits horloge: 33MHz fonctionnalités: pm msi bus_master cap_list configuration: driver=snd_hda_intel latency=32 ressources: irq:128 mémoire:df12-df123fff mémoire:df10-df10 ... $ aplay -l Liste des Périphériques Matériels PLAYBACK carte 0: PCH [HDA Intel PCH], périphérique 0: ALC269VB Analog [ALC269VB Analog] Sous-périphériques: 0/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 3: HDMI 0 [HDMI 0] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 7: HDMI 1 [HDMI 1] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 8: HDMI 2 [HDMI 2] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 9: HDMI 3 [HDMI 3] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 10: HDMI 4 [HDMI 4] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 $ arecord -l Liste des Périphériques Matériels CAPTURE carte 0: PCH [HDA Intel PCH], périphérique 0: ALC269VB Analog [ALC269VB Analog] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 1: UM1 [BIRO UM1], périphérique 0: USB Audio [USB Audio] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 $ lsmod |grep hda -i snd_hda_ext_core 24576 1 snd_soc_skl snd_hda_codec_hdmi 49152 1 snd_hda_codec_realtek 106496 1 snd_hda_codec_generic73728 1 snd_hda_codec_realtek snd_hda_intel 40960 7 snd_hda_codec 126976 4 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek snd_hda_core 81920 7 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_ext_core,snd_hda_codec,snd_hda_codec_realtek,snd_soc_skl snd_hwdep 20480 2 snd_usb_audio,snd_hda_codec snd_pcm98304 11 snd_hda_codec_hdmi,snd_hda_intel,snd_usb_audio,snd_hda_ext_core,snd_hda_codec,snd_soc_core,snd_soc_skl,snd_hda_core,snd_pcm_dmaengine snd81920 28 snd_hda_codec_generic,snd_seq,snd_seq_device,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_usb_audio,snd_usbmidi_lib,snd_hda_codec,snd_hda_codec_realtek,snd_timer,snd_compress,snd_soc_core,snd_pcm,snd_rawmidi Package: pulseaudio Version: 1:12.2-0ubuntu4 Package: alsa-base Version: 1.0.25+dfsg-0ubuntu5 Package: alsa-firmware-loaders Version: 1.1.3-1 Package: udev Version: 239-7ubuntu10.4 To manage notifications about this bug go to:
[Touch-packages] [Bug 1810689] Re: HDA Intel PCH / Realtek ALC269VB not seen by pulseaudio (whereas alsa see it) after ubuntu 18.10 upgrade
Here it is ! $ sudo LANG=LC dpkg -l > /tmp/allpackages.txt ** Attachment added: "allpackages.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1810689/+attachment/5227570/+files/allpackages.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1810689 Title: HDA Intel PCH / Realtek ALC269VB not seen by pulseaudio (whereas alsa see it) after ubuntu 18.10 upgrade Status in pulseaudio package in Ubuntu: Incomplete Bug description: I was using ubuntu 18.04 on my computer (and previously 17.10), and I got the sound card working correctly with pulseaudio. After upgrading to 18.10, pulseaudio interface only detect my usb microphone (BIRO UM1), but it does not detect my computer internal sound card, either for sinking or as a source. I only have a "fictive sink". I have done some experiments: using pacmd, if I try to `load-module module-udev-detect`, nothing happens, and `journalctl --user-unit pulseaudio.service` tells me that the module was already loaded and refuse to load again. If I use `load-module module-detect` the sound card is detected but does not seems to work correctly ! If I use `load-module module-alsa-sink device=default` and `load-module module-alsa-source device=default` my sound card is seens and works as expected. So the problem seems with the module-udev-detect not doing its job correctly (or not having necessary rules ?) My system: $ lsb_release -a LSB Version: core-9.20170808ubuntu1-noarch:printing-9.20170808ubuntu1-noarch:security-9.20170808ubuntu1-noarch Distributor ID: Ubuntu Description: Ubuntu 18.10 Release: 18.10 Codename: cosmic $ uname -a Linux tignasse 4.18.0-13-generic #14-Ubuntu SMP Wed Dec 5 09:04:24 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo lshw ... *-multimedia description: Audio device produit: Sunrise Point-LP HD Audio fabriquant: Intel Corporation identifiant matériel: 1f.3 information bus: pci@:00:1f.3 version: 21 bits: 64 bits horloge: 33MHz fonctionnalités: pm msi bus_master cap_list configuration: driver=snd_hda_intel latency=32 ressources: irq:128 mémoire:df12-df123fff mémoire:df10-df10 ... $ aplay -l Liste des Périphériques Matériels PLAYBACK carte 0: PCH [HDA Intel PCH], périphérique 0: ALC269VB Analog [ALC269VB Analog] Sous-périphériques: 0/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 3: HDMI 0 [HDMI 0] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 7: HDMI 1 [HDMI 1] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 8: HDMI 2 [HDMI 2] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 9: HDMI 3 [HDMI 3] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 10: HDMI 4 [HDMI 4] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 $ arecord -l Liste des Périphériques Matériels CAPTURE carte 0: PCH [HDA Intel PCH], périphérique 0: ALC269VB Analog [ALC269VB Analog] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 1: UM1 [BIRO UM1], périphérique 0: USB Audio [USB Audio] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 $ lsmod |grep hda -i snd_hda_ext_core 24576 1 snd_soc_skl snd_hda_codec_hdmi 49152 1 snd_hda_codec_realtek 106496 1 snd_hda_codec_generic73728 1 snd_hda_codec_realtek snd_hda_intel 40960 7 snd_hda_codec 126976 4 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek snd_hda_core 81920 7 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_ext_core,snd_hda_codec,snd_hda_codec_realtek,snd_soc_skl snd_hwdep 20480 2 snd_usb_audio,snd_hda_codec snd_pcm98304 11 snd_hda_codec_hdmi,snd_hda_intel,snd_usb_audio,snd_hda_ext_core,snd_hda_codec,snd_soc_core,snd_soc_skl,snd_hda_core,snd_pcm_dmaengine snd81920 28 snd_hda_codec_generic,snd_seq,snd_seq_device,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_usb_audio,snd_usbmidi_lib,snd_hda_codec,snd_hda_codec_realtek,snd_timer,snd_compress,snd_soc_core,snd_pcm,snd_rawmidi Package: pulseaudio Version: 1:12.2-0ubuntu4 Package: alsa-base Version: 1.0.25+dfsg-0ubuntu5 Package: alsa-firmware-loaders Version: 1.1.3-1 Package: udev Version: 239-7ubuntu10.4 To manage notifications about this bug go to:
[Touch-packages] [Bug 1810689] [NEW] HDA Intel PCH / Realtek ALC269VB not seen by pulseaudio (whereas alsa see it) after ubuntu 18.10 upgrade
Public bug reported: I was using ubuntu 18.04 on my computer (and previously 17.10), and I got the sound card working correctly with pulseaudio. After upgrading to 18.10, pulseaudio interface only detect my usb microphone (BIRO UM1), but it does not detect my computer internal sound card, either for sinking or as a source. I only have a "fictive sink". I have done some experiments: using pacmd, if I try to `load-module module-udev-detect`, nothing happens, and `journalctl --user-unit pulseaudio.service` tells me that the module was already loaded and refuse to load again. If I use `load-module module-detect` the sound card is detected but does not seems to work correctly ! If I use `load-module module-alsa-sink device=default` and `load-module module-alsa-source device=default` my sound card is seens and works as expected. So the problem seems with the module-udev-detect not doing its job correctly (or not having necessary rules ?) My system: $ lsb_release -a LSB Version: core-9.20170808ubuntu1-noarch:printing-9.20170808ubuntu1-noarch:security-9.20170808ubuntu1-noarch Distributor ID: Ubuntu Description:Ubuntu 18.10 Release:18.10 Codename: cosmic $ uname -a Linux tignasse 4.18.0-13-generic #14-Ubuntu SMP Wed Dec 5 09:04:24 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo lshw ... *-multimedia description: Audio device produit: Sunrise Point-LP HD Audio fabriquant: Intel Corporation identifiant matériel: 1f.3 information bus: pci@:00:1f.3 version: 21 bits: 64 bits horloge: 33MHz fonctionnalités: pm msi bus_master cap_list configuration: driver=snd_hda_intel latency=32 ressources: irq:128 mémoire:df12-df123fff mémoire:df10-df10 ... $ aplay -l Liste des Périphériques Matériels PLAYBACK carte 0: PCH [HDA Intel PCH], périphérique 0: ALC269VB Analog [ALC269VB Analog] Sous-périphériques: 0/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 3: HDMI 0 [HDMI 0] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 7: HDMI 1 [HDMI 1] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 8: HDMI 2 [HDMI 2] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 9: HDMI 3 [HDMI 3] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 10: HDMI 4 [HDMI 4] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 $ arecord -l Liste des Périphériques Matériels CAPTURE carte 0: PCH [HDA Intel PCH], périphérique 0: ALC269VB Analog [ALC269VB Analog] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 1: UM1 [BIRO UM1], périphérique 0: USB Audio [USB Audio] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 $ lsmod |grep hda -i snd_hda_ext_core 24576 1 snd_soc_skl snd_hda_codec_hdmi 49152 1 snd_hda_codec_realtek 106496 1 snd_hda_codec_generic73728 1 snd_hda_codec_realtek snd_hda_intel 40960 7 snd_hda_codec 126976 4 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek snd_hda_core 81920 7 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_ext_core,snd_hda_codec,snd_hda_codec_realtek,snd_soc_skl snd_hwdep 20480 2 snd_usb_audio,snd_hda_codec snd_pcm98304 11 snd_hda_codec_hdmi,snd_hda_intel,snd_usb_audio,snd_hda_ext_core,snd_hda_codec,snd_soc_core,snd_soc_skl,snd_hda_core,snd_pcm_dmaengine snd81920 28 snd_hda_codec_generic,snd_seq,snd_seq_device,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_usb_audio,snd_usbmidi_lib,snd_hda_codec,snd_hda_codec_realtek,snd_timer,snd_compress,snd_soc_core,snd_pcm,snd_rawmidi Package: pulseaudio Version: 1:12.2-0ubuntu4 Package: alsa-base Version: 1.0.25+dfsg-0ubuntu5 Package: alsa-firmware-loaders Version: 1.1.3-1 Package: udev Version: 239-7ubuntu10.4 ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1810689 Title: HDA Intel PCH / Realtek ALC269VB not seen by pulseaudio (whereas alsa see it) after ubuntu 18.10 upgrade Status in pulseaudio package in Ubuntu: New Bug description: I was using ubuntu 18.04 on my computer (and previously 17.10), and I got the sound card working correctly with pulseaudio. After upgrading to 18.10, pulseaudio interface only detect my usb microphone (BIRO UM1), but it does not detect my computer internal sound card, either for sinking or as a source. I only have a "fictive sink". I have done some
[Touch-packages] [Bug 1779582] Re: Unable to create unpriviledged container
I close it for it does not happen with other name. So there should have been a specific problem for the first vm, which maybe pre-exists in some way. ** Changed in: lxc (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1779582 Title: Unable to create unpriviledged container Status in lxc package in Ubuntu: Invalid Bug description: I already have a lot of unpriviledged container initialized while on versions prior to 18.04. I normally got all necessary pieces: $ cat /etc/subuid alex:165536:65536 $ cat /etc/subgid alex:165536:65536 $ cat .config/lxc/default.conf lxc.net.0.type = veth lxc.net.0.link = lxcbr0 lxc.net.0.flags = up lxc.net.0.hwaddr = 00:16:3e:xx:xx:xx lxc.idmap = u 0 165536 65536 lxc.idmap = g 0 165536 65536 I tried to create a new container and it failed. $ lxc-create -n gym -l DEBUG -t download -- -d ubuntu -r xenial -a amd64 Error creating container gym $ cat .local/share/lxc/gym/gym.log lxc-create gym 20180701213443.653 INFO lxc_confile - confile.c:set_config_idmaps:1666 - Read uid map: type u nsid 0 hostid 165536 range 65536 lxc-create gym 20180701213443.653 INFO lxc_confile - confile.c:set_config_idmaps:1666 - Read uid map: type g nsid 0 hostid 165536 range 65536 lxc-create gym 20180701213443.653 DEBUGlxc_conf - conf.c:chown_mapped_root:3086 - trying to chown "/home/alex/.local/share/lxc/gym" to 1001 I got this: $ ls -ld .local/share/lxc/gym drwxr-xr-x 2 165536 alex 4096 juil. 1 22:34 .local/share/lxc/gym So I don't know where it's failing and why ! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lxc 3.0.1-0ubuntu1~18.04.1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Jul 1 22:36:11 2018 InstallationDate: Installed on 2015-11-10 (964 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) KernLog: PackageArchitecture: all SourcePackage: lxc UpgradeStatus: Upgraded to bionic on 2018-05-04 (58 days ago) defaults.conf: lxc.net.0.type = veth lxc.net.0.link = lxcbr0 lxc.net.0.flags = up lxc.net.0.hwaddr = 00:16:3e:xx:xx:xx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1779582/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1779582] Re: Unable to create unpriviledged container
Here it is ! But 1. at the time being a container named gym already exist (for I used lxc-copy to create it) So I tried: $ lxc-create -n gym2 -o lxc.debug -l DEBUG -t download -- -d ubuntu -r xenial -a amd64 and to my surprise it worked. So there might have been something specific to the "gym" folder and I propose to close the ticket ! ** Attachment added: "lxc.debug" https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1779582/+attachment/5159146/+files/lxc.debug -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1779582 Title: Unable to create unpriviledged container Status in lxc package in Ubuntu: Invalid Bug description: I already have a lot of unpriviledged container initialized while on versions prior to 18.04. I normally got all necessary pieces: $ cat /etc/subuid alex:165536:65536 $ cat /etc/subgid alex:165536:65536 $ cat .config/lxc/default.conf lxc.net.0.type = veth lxc.net.0.link = lxcbr0 lxc.net.0.flags = up lxc.net.0.hwaddr = 00:16:3e:xx:xx:xx lxc.idmap = u 0 165536 65536 lxc.idmap = g 0 165536 65536 I tried to create a new container and it failed. $ lxc-create -n gym -l DEBUG -t download -- -d ubuntu -r xenial -a amd64 Error creating container gym $ cat .local/share/lxc/gym/gym.log lxc-create gym 20180701213443.653 INFO lxc_confile - confile.c:set_config_idmaps:1666 - Read uid map: type u nsid 0 hostid 165536 range 65536 lxc-create gym 20180701213443.653 INFO lxc_confile - confile.c:set_config_idmaps:1666 - Read uid map: type g nsid 0 hostid 165536 range 65536 lxc-create gym 20180701213443.653 DEBUGlxc_conf - conf.c:chown_mapped_root:3086 - trying to chown "/home/alex/.local/share/lxc/gym" to 1001 I got this: $ ls -ld .local/share/lxc/gym drwxr-xr-x 2 165536 alex 4096 juil. 1 22:34 .local/share/lxc/gym So I don't know where it's failing and why ! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lxc 3.0.1-0ubuntu1~18.04.1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Jul 1 22:36:11 2018 InstallationDate: Installed on 2015-11-10 (964 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) KernLog: PackageArchitecture: all SourcePackage: lxc UpgradeStatus: Upgraded to bionic on 2018-05-04 (58 days ago) defaults.conf: lxc.net.0.type = veth lxc.net.0.link = lxcbr0 lxc.net.0.flags = up lxc.net.0.hwaddr = 00:16:3e:xx:xx:xx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1779582/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1779582] Re: Unable to create unpriviledged container
I forgot to mention : $ getfacl /home/alex getfacl : suppression du premier « / » des noms de chemins absolus # file: home/alex # owner: alex # group: alex user::rwx user:165536:--x group::r-x mask::r-x other::--- and so all the way down to /home/alex/.local/share/lxc/ Also lxc-copy is working ! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1779582 Title: Unable to create unpriviledged container Status in lxc package in Ubuntu: New Bug description: I already have a lot of unpriviledged container initialized while on versions prior to 18.04. I normally got all necessary pieces: $ cat /etc/subuid alex:165536:65536 $ cat /etc/subgid alex:165536:65536 $ cat .config/lxc/default.conf lxc.net.0.type = veth lxc.net.0.link = lxcbr0 lxc.net.0.flags = up lxc.net.0.hwaddr = 00:16:3e:xx:xx:xx lxc.idmap = u 0 165536 65536 lxc.idmap = g 0 165536 65536 I tried to create a new container and it failed. $ lxc-create -n gym -l DEBUG -t download -- -d ubuntu -r xenial -a amd64 Error creating container gym $ cat .local/share/lxc/gym/gym.log lxc-create gym 20180701213443.653 INFO lxc_confile - confile.c:set_config_idmaps:1666 - Read uid map: type u nsid 0 hostid 165536 range 65536 lxc-create gym 20180701213443.653 INFO lxc_confile - confile.c:set_config_idmaps:1666 - Read uid map: type g nsid 0 hostid 165536 range 65536 lxc-create gym 20180701213443.653 DEBUGlxc_conf - conf.c:chown_mapped_root:3086 - trying to chown "/home/alex/.local/share/lxc/gym" to 1001 I got this: $ ls -ld .local/share/lxc/gym drwxr-xr-x 2 165536 alex 4096 juil. 1 22:34 .local/share/lxc/gym So I don't know where it's failing and why ! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lxc 3.0.1-0ubuntu1~18.04.1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Jul 1 22:36:11 2018 InstallationDate: Installed on 2015-11-10 (964 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) KernLog: PackageArchitecture: all SourcePackage: lxc UpgradeStatus: Upgraded to bionic on 2018-05-04 (58 days ago) defaults.conf: lxc.net.0.type = veth lxc.net.0.link = lxcbr0 lxc.net.0.flags = up lxc.net.0.hwaddr = 00:16:3e:xx:xx:xx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1779582/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1779582] [NEW] Unable to create unpriviledged container
Public bug reported: I already have a lot of unpriviledged container initialized while on versions prior to 18.04. I normally got all necessary pieces: $ cat /etc/subuid alex:165536:65536 $ cat /etc/subgid alex:165536:65536 $ cat .config/lxc/default.conf lxc.net.0.type = veth lxc.net.0.link = lxcbr0 lxc.net.0.flags = up lxc.net.0.hwaddr = 00:16:3e:xx:xx:xx lxc.idmap = u 0 165536 65536 lxc.idmap = g 0 165536 65536 I tried to create a new container and it failed. $ lxc-create -n gym -l DEBUG -t download -- -d ubuntu -r xenial -a amd64 Error creating container gym $ cat .local/share/lxc/gym/gym.log lxc-create gym 20180701213443.653 INFO lxc_confile - confile.c:set_config_idmaps:1666 - Read uid map: type u nsid 0 hostid 165536 range 65536 lxc-create gym 20180701213443.653 INFO lxc_confile - confile.c:set_config_idmaps:1666 - Read uid map: type g nsid 0 hostid 165536 range 65536 lxc-create gym 20180701213443.653 DEBUGlxc_conf - conf.c:chown_mapped_root:3086 - trying to chown "/home/alex/.local/share/lxc/gym" to 1001 I got this: $ ls -ld .local/share/lxc/gym drwxr-xr-x 2 165536 alex 4096 juil. 1 22:34 .local/share/lxc/gym So I don't know where it's failing and why ! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lxc 3.0.1-0ubuntu1~18.04.1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Jul 1 22:36:11 2018 InstallationDate: Installed on 2015-11-10 (964 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) KernLog: PackageArchitecture: all SourcePackage: lxc UpgradeStatus: Upgraded to bionic on 2018-05-04 (58 days ago) defaults.conf: lxc.net.0.type = veth lxc.net.0.link = lxcbr0 lxc.net.0.flags = up lxc.net.0.hwaddr = 00:16:3e:xx:xx:xx ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1779582 Title: Unable to create unpriviledged container Status in lxc package in Ubuntu: New Bug description: I already have a lot of unpriviledged container initialized while on versions prior to 18.04. I normally got all necessary pieces: $ cat /etc/subuid alex:165536:65536 $ cat /etc/subgid alex:165536:65536 $ cat .config/lxc/default.conf lxc.net.0.type = veth lxc.net.0.link = lxcbr0 lxc.net.0.flags = up lxc.net.0.hwaddr = 00:16:3e:xx:xx:xx lxc.idmap = u 0 165536 65536 lxc.idmap = g 0 165536 65536 I tried to create a new container and it failed. $ lxc-create -n gym -l DEBUG -t download -- -d ubuntu -r xenial -a amd64 Error creating container gym $ cat .local/share/lxc/gym/gym.log lxc-create gym 20180701213443.653 INFO lxc_confile - confile.c:set_config_idmaps:1666 - Read uid map: type u nsid 0 hostid 165536 range 65536 lxc-create gym 20180701213443.653 INFO lxc_confile - confile.c:set_config_idmaps:1666 - Read uid map: type g nsid 0 hostid 165536 range 65536 lxc-create gym 20180701213443.653 DEBUGlxc_conf - conf.c:chown_mapped_root:3086 - trying to chown "/home/alex/.local/share/lxc/gym" to 1001 I got this: $ ls -ld .local/share/lxc/gym drwxr-xr-x 2 165536 alex 4096 juil. 1 22:34 .local/share/lxc/gym So I don't know where it's failing and why ! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lxc 3.0.1-0ubuntu1~18.04.1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Jul 1 22:36:11 2018 InstallationDate: Installed on 2015-11-10 (964 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) KernLog: PackageArchitecture: all SourcePackage: lxc UpgradeStatus: Upgraded to bionic on 2018-05-04 (58 days ago) defaults.conf: lxc.net.0.type = veth lxc.net.0.link = lxcbr0 lxc.net.0.flags = up lxc.net.0.hwaddr = 00:16:3e:xx:xx:xx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1779582/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1700500] Re: lxc-net incompatible with systemd-resolved
(Sorry if I misunderstand your answer) I didn't ask how to do it. The bug reports tells that it should be working out of the box, but it's not. This is because ubuntu switched to systemd-revolved and this package do not provide the necessary bridge, which is the configuration bit you provide (and that I already provide in the description). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1700500 Title: lxc-net incompatible with systemd-resolved Status in lxc package in Ubuntu: New Bug description: Symptoms If an lxc container named *mycontainer* runs, it is not accessible using name *mycontainer.lxc*. Causes -- The lxc1 package provides the lxc-net.service which launch a dns-masq process to act as dns providing name resolution to local lxc instances using the .lxc domain. This DNS is however not declared to systemd-resolved, and so .lxc names do not work on a standard ubuntu install. Proposed solution - The lxc1 package should provide a /etc/systemd/resolved.conf.d/lxc.conf with the following content:: [Resolve] DNS=10.0.3.1 Domains=~.lxc DNSSEC=false ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: lxc1 2.0.8-0ubuntu1~17.04.2 Uname: Linux 4.10.16-041016-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jun 26 11:07:24 2017 InstallationDate: Installed on 2015-11-10 (593 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: lxc UpgradeStatus: Upgraded to zesty on 2017-02-25 (120 days ago) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1700500/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1721092] Re: systemd-resolved and dns-masq make CPU 100% when using lxc name resolution
Hello, I tried to get DNS packets using : $ sudo tcpdump -i lxcbr0 -l -vvv dst host 10.0.3.1 and dst port 53 |tee /tmp/tcpdump-dns I then wait until systemd-resolved ate 100% of CPU. But at this time (unfortunately when I noticed it, it may have been eaten CPU for quite a while). However I can't see any strange exchange between systemd- resolved and dnsmasq. I attach all the packets captured by tcpdump. I'm not an expert in networks topics but I'm at ease with linux and cli commands, so feel free to tell me which experiment you would like me to run. ** Attachment added: "tcpdump session between dnsmasq and systemd-resolved" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1721092/+attachment/5044944/+files/tcpdump-dns -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1721092 Title: systemd-resolved and dns-masq make CPU 100% when using lxc name resolution Status in systemd package in Ubuntu: Triaged Bug description: This bug may be a duplicate of https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1688364 but I'm not sure, hence this new entry. It hits while I wanted systemd to resolve the lxc domain to my internal lxc hosts. Step to (maybe) reproduce: - having lxc installed - make some user space lxc container - uncomment the line LXC_DOMAIN="lxc" in /etc/default/lxc-net - restart lxc-net service Now the dnsmasq on 10.0.3.1 should be a dns resolving lxc names. - add a file /etc/systemd/resolved.conf.d/lxc.conf [Resolve] DNS=10.0.3.1 Domains=~.lxc DNSSEC=false - restart systemd-resolved service Now systemd knows it should ask .lxc names to dnsmasq - start an lxc container, let assume it's called my-container - ping it using my-container.lxc it should work After some times, systemd-resolved should use 100% CPU. Commenting the /etc/systemd/resolved.conf.d/lxc.conf file and restarting it makes systemd-resolved never eating resources again. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: systemd 232-21ubuntu5 Uname: Linux 4.10.16-041016-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Oct 3 18:18:56 2017 InstallationDate: Installed on 2015-11-10 (692 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Intel Corporation Skylake Platform ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.16-041016-generic root=UUID=6814e3c1-8cea-4ecc-964d-535fd18782e9 ro quiet splash crashkernel=384M-:128M vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to zesty on 2017-02-25 (219 days ago) dmi.bios.date: 11/06/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.11 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: WhiteTip Mountain1 Fab2 dmi.board.vendor: Topstar dmi.board.version: RVP7 dmi.chassis.asset.tag: Default string dmi.chassis.type: 9 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd11/06/2015:svnIntelCorporation:pnSkylakePlatform:pvr0.1:rvnTopstar:rnWhiteTipMountain1Fab2:rvrRVP7:cvnDefaultstring:ct9:cvrDefaultstring: dmi.product.name: Skylake Platform dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1721092/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1721092] Re: systemd-resolved and dns-masq make CPU 100% when using lxc name resolution
Hello, I verified the bug is still there on my laptop. here are the elements you asked for (see also attached file). - $ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 127.0.0.53 - In case here are installed versions: lxc Version: 2.1.0-0ubuntu1 lxc-common Version: 2.1.0-0ubuntu1 systemd Version: 234-2ubuntu12.1 dnsmasq Version: Version: 2.78-1 ** Attachment added: "systemd-resolve --status" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1721092/+attachment/5044600/+files/systemd-resolve-status -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1721092 Title: systemd-resolved and dns-masq make CPU 100% when using lxc name resolution Status in systemd package in Ubuntu: Incomplete Bug description: This bug may be a duplicate of https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1688364 but I'm not sure, hence this new entry. It hits while I wanted systemd to resolve the lxc domain to my internal lxc hosts. Step to (maybe) reproduce: - having lxc installed - make some user space lxc container - uncomment the line LXC_DOMAIN="lxc" in /etc/default/lxc-net - restart lxc-net service Now the dnsmasq on 10.0.3.1 should be a dns resolving lxc names. - add a file /etc/systemd/resolved.conf.d/lxc.conf [Resolve] DNS=10.0.3.1 Domains=~.lxc DNSSEC=false - restart systemd-resolved service Now systemd knows it should ask .lxc names to dnsmasq - start an lxc container, let assume it's called my-container - ping it using my-container.lxc it should work After some times, systemd-resolved should use 100% CPU. Commenting the /etc/systemd/resolved.conf.d/lxc.conf file and restarting it makes systemd-resolved never eating resources again. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: systemd 232-21ubuntu5 Uname: Linux 4.10.16-041016-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Oct 3 18:18:56 2017 InstallationDate: Installed on 2015-11-10 (692 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Intel Corporation Skylake Platform ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.16-041016-generic root=UUID=6814e3c1-8cea-4ecc-964d-535fd18782e9 ro quiet splash crashkernel=384M-:128M vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to zesty on 2017-02-25 (219 days ago) dmi.bios.date: 11/06/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.11 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: WhiteTip Mountain1 Fab2 dmi.board.vendor: Topstar dmi.board.version: RVP7 dmi.chassis.asset.tag: Default string dmi.chassis.type: 9 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd11/06/2015:svnIntelCorporation:pnSkylakePlatform:pvr0.1:rvnTopstar:rnWhiteTipMountain1Fab2:rvrRVP7:cvnDefaultstring:ct9:cvrDefaultstring: dmi.product.name: Skylake Platform dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1721092/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1721092] Re: systemd-resolved and dns-masq make CPU 100% when using lxc name resolution
Hello, can I do anything for this to progress toward a solution ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1721092 Title: systemd-resolved and dns-masq make CPU 100% when using lxc name resolution Status in systemd package in Ubuntu: New Bug description: This bug may be a duplicate of https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1688364 but I'm not sure, hence this new entry. It hits while I wanted systemd to resolve the lxc domain to my internal lxc hosts. Step to (maybe) reproduce: - having lxc installed - make some user space lxc container - uncomment the line LXC_DOMAIN="lxc" in /etc/default/lxc-net - restart lxc-net service Now the dnsmasq on 10.0.3.1 should be a dns resolving lxc names. - add a file /etc/systemd/resolved.conf.d/lxc.conf [Resolve] DNS=10.0.3.1 Domains=~.lxc DNSSEC=false - restart systemd-resolved service Now systemd knows it should ask .lxc names to dnsmasq - start an lxc container, let assume it's called my-container - ping it using my-container.lxc it should work After some times, systemd-resolved should use 100% CPU. Commenting the /etc/systemd/resolved.conf.d/lxc.conf file and restarting it makes systemd-resolved never eating resources again. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: systemd 232-21ubuntu5 Uname: Linux 4.10.16-041016-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Oct 3 18:18:56 2017 InstallationDate: Installed on 2015-11-10 (692 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Intel Corporation Skylake Platform ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.16-041016-generic root=UUID=6814e3c1-8cea-4ecc-964d-535fd18782e9 ro quiet splash crashkernel=384M-:128M vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to zesty on 2017-02-25 (219 days ago) dmi.bios.date: 11/06/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.11 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: WhiteTip Mountain1 Fab2 dmi.board.vendor: Topstar dmi.board.version: RVP7 dmi.chassis.asset.tag: Default string dmi.chassis.type: 9 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd11/06/2015:svnIntelCorporation:pnSkylakePlatform:pvr0.1:rvnTopstar:rnWhiteTipMountain1Fab2:rvrRVP7:cvnDefaultstring:ct9:cvrDefaultstring: dmi.product.name: Skylake Platform dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1721092/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1721092] [NEW] systemd-resolved and dns-masq make CPU 100% when using lxc name resolution
Public bug reported: This bug may be a duplicate of https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1688364 but I'm not sure, hence this new entry. It hits while I wanted systemd to resolve the lxc domain to my internal lxc hosts. Step to (maybe) reproduce: - having lxc installed - make some user space lxc container - uncomment the line LXC_DOMAIN="lxc" in /etc/default/lxc-net - restart lxc-net service Now the dnsmasq on 10.0.3.1 should be a dns resolving lxc names. - add a file /etc/systemd/resolved.conf.d/lxc.conf [Resolve] DNS=10.0.3.1 Domains=~.lxc DNSSEC=false - restart systemd-resolved service Now systemd knows it should ask .lxc names to dnsmasq - start an lxc container, let assume it's called my-container - ping it using my-container.lxc it should work After some times, systemd-resolved should use 100% CPU. Commenting the /etc/systemd/resolved.conf.d/lxc.conf file and restarting it makes systemd-resolved never eating resources again. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: systemd 232-21ubuntu5 Uname: Linux 4.10.16-041016-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Oct 3 18:18:56 2017 InstallationDate: Installed on 2015-11-10 (692 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Intel Corporation Skylake Platform ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.16-041016-generic root=UUID=6814e3c1-8cea-4ecc-964d-535fd18782e9 ro quiet splash crashkernel=384M-:128M vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to zesty on 2017-02-25 (219 days ago) dmi.bios.date: 11/06/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.11 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: WhiteTip Mountain1 Fab2 dmi.board.vendor: Topstar dmi.board.version: RVP7 dmi.chassis.asset.tag: Default string dmi.chassis.type: 9 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd11/06/2015:svnIntelCorporation:pnSkylakePlatform:pvr0.1:rvnTopstar:rnWhiteTipMountain1Fab2:rvrRVP7:cvnDefaultstring:ct9:cvrDefaultstring: dmi.product.name: Skylake Platform dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1721092 Title: systemd-resolved and dns-masq make CPU 100% when using lxc name resolution Status in systemd package in Ubuntu: New Bug description: This bug may be a duplicate of https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1688364 but I'm not sure, hence this new entry. It hits while I wanted systemd to resolve the lxc domain to my internal lxc hosts. Step to (maybe) reproduce: - having lxc installed - make some user space lxc container - uncomment the line LXC_DOMAIN="lxc" in /etc/default/lxc-net - restart lxc-net service Now the dnsmasq on 10.0.3.1 should be a dns resolving lxc names. - add a file /etc/systemd/resolved.conf.d/lxc.conf [Resolve] DNS=10.0.3.1 Domains=~.lxc DNSSEC=false - restart systemd-resolved service Now systemd knows it should ask .lxc names to dnsmasq - start an lxc container, let assume it's called my-container - ping it using my-container.lxc it should work After some times, systemd-resolved should use 100% CPU. Commenting the /etc/systemd/resolved.conf.d/lxc.conf file and restarting it makes systemd-resolved never eating resources again. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: systemd 232-21ubuntu5 Uname: Linux 4.10.16-041016-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Oct 3 18:18:56 2017 InstallationDate: Installed on 2015-11-10 (692 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Intel Corporation Skylake Platform ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.16-041016-generic root=UUID=6814e3c1-8cea-4ecc-964d-535fd18782e9 ro quiet splash crashkernel=384M-:128M vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to zesty on 2017-02-25 (219 days ago) dmi.bios.date: 11/06/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.11 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: WhiteTip Mountain1 Fab2 dmi.board.vendor: Topstar dmi.board.version: RVP7 dmi.chassis.asset.tag: Default string dmi.chassis.type: 9 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd11/06/2015:svnIntelCorporation:pnSkylakePlatform:pvr0.1:rvnTopstar:rnWhiteTipMountain1Fab2:rvrRVP7:cvnDefaultstring:ct9:cvrDefaultstring:
[Touch-packages] [Bug 1700500] [NEW] lxc-net incompatible with systemd-resolved
Public bug reported: Symptoms If an lxc container named *mycontainer* runs, it is not accessible using name *mycontainer.lxc*. Causes -- The lxc1 package provides the lxc-net.service which launch a dns-masq process to act as dns providing name resolution to local lxc instances using the .lxc domain. This DNS is however not declared to systemd-resolved, and so .lxc names do not work on a standard ubuntu install. Proposed solution - The lxc1 package should provide a /etc/systemd/resolved.conf.d/lxc.conf with the following content:: [Resolve] DNS=10.0.3.1 Domains=~.lxc DNSSEC=false ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: lxc1 2.0.8-0ubuntu1~17.04.2 Uname: Linux 4.10.16-041016-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jun 26 11:07:24 2017 InstallationDate: Installed on 2015-11-10 (593 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: lxc UpgradeStatus: Upgraded to zesty on 2017-02-25 (120 days ago) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1700500 Title: lxc-net incompatible with systemd-resolved Status in lxc package in Ubuntu: New Bug description: Symptoms If an lxc container named *mycontainer* runs, it is not accessible using name *mycontainer.lxc*. Causes -- The lxc1 package provides the lxc-net.service which launch a dns-masq process to act as dns providing name resolution to local lxc instances using the .lxc domain. This DNS is however not declared to systemd-resolved, and so .lxc names do not work on a standard ubuntu install. Proposed solution - The lxc1 package should provide a /etc/systemd/resolved.conf.d/lxc.conf with the following content:: [Resolve] DNS=10.0.3.1 Domains=~.lxc DNSSEC=false ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: lxc1 2.0.8-0ubuntu1~17.04.2 Uname: Linux 4.10.16-041016-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jun 26 11:07:24 2017 InstallationDate: Installed on 2015-11-10 (593 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: lxc UpgradeStatus: Upgraded to zesty on 2017-02-25 (120 days ago) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1700500/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
