Your message dated Fri, 1 Jul 2022 20:50:45 +0100 with message-id <Yr9QFT8Z/[email protected]> and subject line Re: Bug#1014188: bubblewrap: attempt to launch a prgram and get bwrap: Creating new namespace failed: No space left on device has caused the Debian Bug report #1014188, regarding bubblewrap: attempt to launch a prgram and get bwrap: Creating new namespace failed: No space left on device to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 1014188: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014188 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: bubblewrap Version: 0.6.2-1 Severity: important X-Debbugs-Cc: [email protected] Dear Maintainer, Attempt to launch Epiphany or DevHelp from a command line and receive this error: "bwrap: Creating new namespace failed: No space left on device" I have no idea why it shows I've use 36.1 GiB of 91.1GiB of disk space, I should have room? If I click on the Icon for either program it doesn't even appear to do anything at all. -- Package-specific info: Permissions of /usr/bin/bwrap: -rwxr-xr-x 1 root root 67984 May 11 09:07 /usr/bin/bwrap /etc/sysctl.d/*-bubblewrap.conf: cat: '/etc/sysctl.d/*-bubblewrap.conf': No such file or directory /usr/lib/sysctl.d/50-bubblewrap.conf: # Enable unprivileged creation of new user namespaces in older Debian # kernels. # # If this is not desired, copy this file to # /etc/sysctl.d/50-bubblewrap.conf and change the value of this parameter # to 0, then use dpkg-statoverride to make /usr/bin/bwrap setuid root. # # For more details see https://deb.li/bubblewrap or # /usr/share/doc/bubblewrap/README.Debian kernel.unprivileged_userns_clone=1 /proc/sys/kernel/unprivileged_userns_clone: 1 /proc/sys/user/max_cgroup_namespaces: 27347 /proc/sys/user/max_ipc_namespaces: 27347 /proc/sys/user/max_mnt_namespaces: 27347 /proc/sys/user/max_net_namespaces: 27347 /proc/sys/user/max_pid_namespaces: 27347 /proc/sys/user/max_time_namespaces: 27347 /proc/sys/user/max_user_namespaces: 0 /proc/sys/user/max_uts_namespaces: 27347 -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.18.0-2-rt-amd64 (SMP w/1 CPU thread; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages bubblewrap depends on: ii libc6 2.33-7 ii libcap2 1:2.44-1 ii libselinux1 3.4-1 Versions of packages bubblewrap recommends: ii procps 2:3.3.17-7+b1 bubblewrap suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---On Fri, 01 Jul 2022 at 12:58:18 -0500, Tim McConnell wrote: > "bwrap: Creating new namespace failed: No space left on device" This is the error you get if the limit on user namespaces (or any other limited resource) is exceeded. The error message that comes from the kernel is a bit misleading; I have a merge request open upstream to special-case this error condition to have a different error message, but it hasn't been reviewed by a maintainer. > -- Package-specific info: ... > /proc/sys/user/max_user_namespaces: > 0 If you've set the maximum number of user namespaces to 0, then bubblewrap cannot work (unless it's setuid root, which I wouldn't recommend). See /usr/share/doc/bubblewrap/README.Debian.gz for details. Other container-based tools probably also can't work with this limit set to 0. I would recommend leaving it at its default (which depends on how much RAM you have, but is typically in the tens of thousands). smcv
--- End Message ---
