[Bug 1965680] Re: it says install now when it should say continue
Ok I connected this to the internet and manually copied the oauth token over and had the info sent. I hope all of this is useful to fix the issue with the continue button's text. These are files from the page before the page with the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965680 Title: it says install now when it should say continue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1965680/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965680] UbiquityPartman.txt
apport information ** Attachment added: "UbiquityPartman.txt" https://bugs.launchpad.net/bugs/1965680/+attachment/5571293/+files/UbiquityPartman.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965680 Title: it says install now when it should say continue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1965680/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965680] UbiquitySyslog.txt
apport information ** Attachment added: "UbiquitySyslog.txt" https://bugs.launchpad.net/bugs/1965680/+attachment/5571294/+files/UbiquitySyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965680 Title: it says install now when it should say continue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1965680/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965680] UbiquityDm.txt
apport information ** Attachment added: "UbiquityDm.txt" https://bugs.launchpad.net/bugs/1965680/+attachment/5571292/+files/UbiquityDm.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965680 Title: it says install now when it should say continue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1965680/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965680] UbiquityDebug.txt
apport information ** Attachment added: "UbiquityDebug.txt" https://bugs.launchpad.net/bugs/1965680/+attachment/5571291/+files/UbiquityDebug.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965680 Title: it says install now when it should say continue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1965680/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965680] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1965680/+attachment/5571290/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965680 Title: it says install now when it should say continue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1965680/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965680] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1965680/+attachment/5571289/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965680 Title: it says install now when it should say continue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1965680/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965680] Re: it says install now when it should say continue
apport information ** Tags added: apport-collected impish ubiquity-21.10.10 ubuntu ** Description changed: - After you select that you want to erase everything and install over it - the button in the lower right corner says "Install Now". This should say - "Continue" because you still need to pick which disk to erase. It saying - "Install Now" makes it seem like that is the last step before it will - start writing like it has a disk in mind already. It's kind of scary to - press this button to proceed with the installation. + After you select that you want to erase everything and install over it the button in the lower right corner says "Install Now". This should say "Continue" because you still need to pick which disk to erase. It saying "Install Now" makes it seem like that is the last step before it will start writing like it has a disk in mind already. It's kind of scary to press this button to proceed with the installation. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu70 + Architecture: amd64 + CasperMD5CheckResult: pass + CasperVersion: 1.465 + DistroRelease: Ubuntu 21.10 + InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- + LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) + NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair + Package: ubiquity 21.10.10 [modified: lib/partman/automatically_partition/question] + PackageArchitecture: amd64 + ProcEnviron: + TERM=linux + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=C.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 + Tags: impish ubiquity-21.10.10 ubuntu + Uname: Linux 5.13.0-19-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Casper.txt" https://bugs.launchpad.net/bugs/1965680/+attachment/5571288/+files/Casper.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965680 Title: it says install now when it should say continue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1965680/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965680] Re: it says install now when it should say continue
Am I reporting this to the right repository? ubiquity is the program that runs when you try to install ubuntu from a live cd right? What information do you want? I have my cell phone camera ready to go. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965680 Title: it says install now when it should say continue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1965680/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965680] Re: it says install now when it should say continue
It says ERROR: connecting to Launchpad failed: Unable to find the server at launchpad.net What now? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965680 Title: it says install now when it should say continue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1965680/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965681] [NEW] ntfs resize takes forever
Public bug reported: When I select that it should erase a disk and install there it queries my disks to see if my other disks with ntfs on them can be resized. This is unnecessary since I'm not using those disks. It also takes forever. It basically makes installing ubuntu impossible unless I disconnect those disks or I go and kill the pids associated with querying that information. Attached is "px auxfww" output. Does this information have to be queried or can it be queried in the background? ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Attachment added: "PXL_20220317_171806443.jpg" https://bugs.launchpad.net/bugs/1965681/+attachment/5571069/+files/PXL_20220317_171806443.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965681 Title: ntfs resize takes forever To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1965681/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965680] [NEW] it says install now when it should say continue
Public bug reported: After you select that you want to erase everything and install over it the button in the lower right corner says "Install Now". This should say "Continue" because you still need to pick which disk to erase. It saying "Install Now" makes it seem like that is the last step before it will start writing like it has a disk in mind already. It's kind of scary to press this button to proceed with the installation. ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965680 Title: it says install now when it should say continue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1965680/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870514] Re: update containerd:amd64 1.3.3-0 stops docker daemon
What does rls-ff-incoming mean? Is this something that can be fixed everywhere? I'm pretty sure it's something that happens to mysql also: https://askubuntu.com/q/1037285 A workaround for this seems to be to use the docker snap package. snapd seems to keep stuff running.. at least when there isn't some horrible apparmor issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870514 Title: update containerd:amd64 1.3.3-0 stops docker daemon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd/+bug/1870514/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880021] Re: docker containers can't read any files (snap)
*** This bug is a duplicate of bug 1880025 *** https://bugs.launchpad.net/bugs/1880025 ** This bug has been marked a duplicate of bug 1880025 apparmor="DENIED" on docker container files -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880021 Title: docker containers can't read any files (snap) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker/+bug/1880021/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880022] [NEW] pid file prevents starting the docker snap
Public bug reported: docker seems to not be able to start because of a pid file that was left behind. This only happened on one of my hosts and hasn't happened again after fixing it. I get these logs over and over again: 2020-04-30T06:47:38Z systemd[1]: Started Service for snap application docker.dockerd. 2020-04-30T06:47:49Z docker.dockerd[1127]: Error starting daemon: pid file found, ensure docker is not running or delete /var/snap/docker/423/run/docker.pid 2020-04-30T06:47:49Z systemd[1]: snap.docker.dockerd.service: Main process exited, code=exited, status=1/FAILURE 2020-04-30T06:47:49Z systemd[1]: snap.docker.dockerd.service: Failed with result 'exit-code'. 2020-04-30T06:47:50Z systemd[1]: snap.docker.dockerd.service: Service RestartSec=100ms expired, scheduling restart. 2020-04-30T06:47:50Z systemd[1]: snap.docker.dockerd.service: Scheduled restart job, restart counter is at 1. 2020-04-30T06:47:50Z systemd[1]: Stopped Service for snap application docker.dockerd. 2020-04-30T06:47:50Z systemd[1]: Started Service for snap application docker.dockerd. 2020-04-30T06:47:50Z docker.dockerd[1325]: Error starting daemon: pid file found, ensure docker is not running or delete /var/snap/docker/423/run/docker.pid 2020-04-30T06:47:50Z systemd[1]: snap.docker.dockerd.service: Main process exited, code=exited, status=1/FAILURE 2020-04-30T06:47:50Z systemd[1]: snap.docker.dockerd.service: Failed with result 'exit-code'. 2020-04-30T06:47:50Z systemd[1]: snap.docker.dockerd.service: Service RestartSec=100ms expired, scheduling restart. 2020-04-30T06:47:50Z systemd[1]: snap.docker.dockerd.service: Scheduled restart job, restart counter is at 2. 2020-04-30T06:47:50Z systemd[1]: Stopped Service for snap application docker.dockerd. 2020-04-30T06:47:50Z systemd[1]: Started Service for snap application docker.dockerd. 2020-04-30T06:47:50Z docker.dockerd[1390]: Error starting daemon: pid file found, ensure docker is not running or delete /var/snap/docker/423/run/docker.pid 2020-04-30T06:47:50Z systemd[1]: snap.docker.dockerd.service: Main process exited, code=exited, status=1/FAILURE 2020-04-30T06:47:50Z systemd[1]: snap.docker.dockerd.service: Failed with result 'exit-code'. 2020-04-30T06:47:51Z systemd[1]: snap.docker.dockerd.service: Service RestartSec=100ms expired, scheduling restart. 2020-04-30T06:47:51Z systemd[1]: snap.docker.dockerd.service: Scheduled restart job, restart counter is at 3. 2020-04-30T06:47:51Z systemd[1]: Stopped Service for snap application docker.dockerd. 2020-04-30T06:47:51Z systemd[1]: Started Service for snap application docker.dockerd. 2020-04-30T06:47:51Z docker.dockerd[1452]: Error starting daemon: pid file found, ensure docker is not running or delete /var/snap/docker/423/run/docker.pid 2020-04-30T06:47:51Z systemd[1]: snap.docker.dockerd.service: Main process exited, code=exited, status=1/FAILURE 2020-04-30T06:47:51Z systemd[1]: snap.docker.dockerd.service: Failed with result 'exit-code'. 2020-04-30T06:47:51Z systemd[1]: snap.docker.dockerd.service: Service RestartSec=100ms expired, scheduling restart. 2020-04-30T06:47:51Z systemd[1]: snap.docker.dockerd.service: Scheduled restart job, restart counter is at 4. 2020-04-30T06:47:51Z systemd[1]: Stopped Service for snap application docker.dockerd. 2020-04-30T06:47:51Z systemd[1]: Started Service for snap application docker.dockerd. 2020-04-30T06:47:51Z docker.dockerd[1511]: Error starting daemon: pid file found, ensure docker is not running or delete /var/snap/docker/423/run/docker.pid 2020-04-30T06:47:51Z systemd[1]: snap.docker.dockerd.service: Main process exited, code=exited, status=1/FAILURE 2020-04-30T06:47:51Z systemd[1]: snap.docker.dockerd.service: Failed with result 'exit-code'. 2020-04-30T06:47:52Z systemd[1]: snap.docker.dockerd.service: Service RestartSec=100ms expired, scheduling restart. 2020-04-30T06:47:52Z systemd[1]: snap.docker.dockerd.service: Scheduled restart job, restart counter is at 5. 2020-04-30T06:47:52Z systemd[1]: Stopped Service for snap application docker.dockerd. 2020-04-30T06:47:52Z systemd[1]: Started Service for snap application docker.dockerd. 2020-04-30T06:47:52Z docker.dockerd[1573]: Error starting daemon: pid file found, ensure docker is not running or delete /var/snap/docker/423/run/docker.pid 2020-04-30T06:47:52Z systemd[1]: snap.docker.dockerd.service: Main process exited, code=exited, status=1/FAILURE 2020-04-30T06:47:52Z systemd[1]: snap.docker.dockerd.service: Failed with result 'exit-code'. 2020-04-30T06:47:52Z systemd[1]: snap.docker.dockerd.service: Service RestartSec=100ms expired, scheduling restart. 2020-04-30T06:47:52Z systemd[1]: snap.docker.dockerd.service: Scheduled restart job, restart counter is at 6. 2020-04-30T06:47:52Z systemd[1]: Stopped Service for snap application docker.dockerd. 2020-04-30T06:47:52Z systemd[1]: snap.docker.dockerd.service: Start request repeated too quickly. 2020-04-30T06:47:52Z systemd[1]: snap.docker.dockerd.ser
[Bug 1880021] [NEW] docker containers can't read any files (snap)
Public bug reported: [ 905.842011] audit: type=1400 audit(1590090428.258:167): apparmor="DENIED" operation="open" profile="snap.docker.dockerd" name="/usr/local/bin/start_ipfs" pid=8466 comm="start_ipfs" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 My containers are failing to start because app armor is blocking them from being able to read anything from their image. This is a relatively recent problem. docker 18.09.9423latest/stablecanonical✓ - ** Affects: docker (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880021 Title: docker containers can't read any files (snap) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker/+bug/1880021/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870876] Re: docker stopped when containerd updated
Maybe a workaround fix could be to restart ubuntu if dependent services had to be stopped to update something? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870876 Title: docker stopped when containerd updated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1870876/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870876] Re: docker stopped when containerd updated
Here are people who are hit by this except for mysql: https://askubuntu.com/questions/1037285/starting-daily-apt-upgrade-and-clean-activities-stopping-mysql-service -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870876 Title: docker stopped when containerd updated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1870876/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870876] Re: docker stopped when containerd updated
attaching unattended-upgrades-dpkg.log ** Attachment added: "/var/log/unattended-upgrades/unattended-upgrades-dpkg.log" https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1870876/+attachment/5346860/+files/unattended-upgrades-dpkg.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870876 Title: docker stopped when containerd updated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1870876/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870876] [NEW] docker stopped when containerd updated
Public bug reported: When containerd was updated in my bionic instance it stopped docker then stopped containerd. When it was done updating containerd it brought it back online. docker stayed stopped. 2020-04-03 06:20:32,973 INFO Packages that will be upgraded: apport containerd python3-apport python3-problem-report An eoan installation that didn't have this problem had this line: 2020-04-03 06:06:01,612 INFO Packages that will be upgraded: apport python3-apport python3-problem-report So the main difference is that containerd was updated. At the end of this systemctl --all reported docker as: docker.service loadedinactive dead and containerd as: containerd.service loadedactive running Description:Ubuntu 18.04.4 LTS Release:18.04 unattended-upgrades: Installed: 1.1ubuntu1.18.04.14 Candidate: 1.1ubuntu1.18.04.14 Version table: *** 1.1ubuntu1.18.04.14 500 500 http://us-central1.gce.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.1ubuntu1 500 500 http://us-central1.gce.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ** Affects: unattended-upgrades (Ubuntu) Importance: Undecided Status: New ** Attachment added: "journalctl --since "2020-04-03 06:33:52" --until "2020-04-03 06:54:50" >journalctl.log" https://bugs.launchpad.net/bugs/1870876/+attachment/5346855/+files/journalctl.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870876 Title: docker stopped when containerd updated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1870876/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870876] Re: docker stopped when containerd updated
attaching unattended-upgrades.log ** Attachment added: "/var/log/unattended-upgrades/unattended-upgrades.log" https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1870876/+attachment/5346859/+files/unattended-upgrades.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870876 Title: docker stopped when containerd updated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1870876/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821540] Re: docker can't stop containers because of apparmor
It's working now. I'm not sure why. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821540 Title: docker can't stop containers because of apparmor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1821540/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821540] Re: docker can't stop containers because of apparmor
I think the change in this commit isn't in my app armor profile.
https://github.com/moby/moby/commit/4822fb1e2423d88cdf0ad5d039b8fd3274b05401
What does yours look like?
$ cat /etc/apparmor.d/docker
#include
profile docker-default flags=(attach_disconnected,mediate_deleted) {
#include
network,
capability,
file,
umount,
deny @{PROC}/* w, # deny write for all files directly in /proc (not in a
subdir)
# deny write to files not in /proc//** or /proc/sys/**
deny
@{PROC}/{[^1-9],[^1-9][^0-9],[^1-9s][^0-9y][^0-9s],[^1-9][^0-9][^0-9][^0-9]*}/**
w,
deny @{PROC}/sys/[^k]** w, # deny /proc/sys except /proc/sys/k* (effectively
/proc/sys/kernel)
deny @{PROC}/sys/kernel/{?,??,[^s][^h][^m]**} w, # deny everything except
shm* in /proc/sys/kernel/
deny @{PROC}/sysrq-trigger rwklx,
deny @{PROC}/mem rwklx,
deny @{PROC}/kmem rwklx,
deny @{PROC}/kcore rwklx,
deny mount,
deny /sys/[^f]*/** wklx,
deny /sys/f[^s]*/** wklx,
deny /sys/fs/[^c]*/** wklx,
deny /sys/fs/c[^g]*/** wklx,
deny /sys/fs/cg[^r]*/** wklx,
deny /sys/firmware/efi/efivars/** rwklx,
deny /sys/kernel/security/** rwklx,
# suppress ptrace denials when using 'docker ps' or using 'ps' inside a
container
ptrace (trace,read) peer=docker-default,
}
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821540
Title:
docker can't stop containers because of apparmor
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1821540/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821540] [NEW] docker can't stop containers because of apparmor
Public bug reported: Docker can't stop containers because it can't send a signal to it because of apparmor. There is also a spelling mistake in the error message. $ docker stop 35 Error response from daemon: cannot stop container: 35: Cannot kill container 352331e095ca6de50eefaaa4ff3a2b81f056daf71ccb1e2b70a19ea4c1832f5a: unknown error after kill: docker-runc did not terminate sucessfully: container_linux.go:387: signaling init process caused "permission denied" : unknown $ dmesg [1092035.379443] audit: type=1400 audit(1553460324.354:286): apparmor="DENIED" operation="signal" profile="docker-default" pid=15466 comm="docker-runc" requested_mask="receive" denied_mask="receive" signal=kill peer="unconfined" $ lsb_release -rd Description:Ubuntu 18.04.2 LTS Release:18.04 $ apt-cache policy docker.io docker.io: Installed: 18.09.2-0ubuntu1~18.04.1 Candidate: 18.09.2-0ubuntu1~18.04.1 Version table: *** 18.09.2-0ubuntu1~18.04.1 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages 100 /var/lib/dpkg/status 18.06.1-0ubuntu1.2~18.04.1 500 500 http://security.ubuntu.com/ubuntu bionic-security/universe amd64 Packages 17.12.1-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages ** Affects: docker.io (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821540 Title: docker can't stop containers because of apparmor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1821540/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802979] [NEW] journald log driver does not support reading
Public bug reported: I can't get logs out of containers that use journald using the `docker logs` command. ``` $ docker logs fa95590f3c6b Error response from daemon: configured logging driver does not support reading ``` The journald logging driver usually supports reading logs. According to this issue on github (https://github.com/moby/moby/issues/31404) it only works if the binary is properly linked. The docker binary from this package doesn't seem to support it. ** Affects: docker.io (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802979 Title: journald log driver does not support reading To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1802979/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1258597] Re: Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is set is no longer supported.
What actually has to be done for something like this to be fixed? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1258597 Title: Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is set is no longer supported. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1258597/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1162471] [NEW] Subscription Request lacks pertinent information
Public bug reported: Description:Ubuntu 12.10 Release:12.10 empathy: Installed: 3.6.0.3-0ubuntu1 Candidate: 3.6.0.3-0ubuntu1 Version table: *** 3.6.0.3-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ quantal/main amd64 Packages 100 /var/lib/dpkg/status The Subscription Request dialogue includes almost no information. There are no links to what service it's talking about. There are no links to this person's profile page. I also don't see an option to table to request. Do I have to respond to it immediately? Is closing the dialogue the same as declining it? It's also not clear how to get to a list of currently active subscription requests. I'm pretty sure I had a bunch of subscription requests but I am unsure where they went or what happened to them after I closed them. Why is it called a subscription request anyway? ** Affects: empathy (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1162471 Title: Subscription Request lacks pertinent information To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1162471/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
