[Bug 1966889] Re: docker-build containers do not have logging driver configure
** Changed in: docker.io (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966889 Title: docker-build containers do not have logging driver configure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1966889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966889] Re: docker-build containers do not have logging driver configure
There are global defaults for logging which you can configure in daemon.json (log-driver, log-level, log-opt), but none of these are used when building images. This was intentionally changed in https://github.com/moby/moby/pull/29552, which has been included since Docker 17.04.0 -- I imagine your previous cases where this worked were likely on older versions of Docker than that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966889 Title: docker-build containers do not have logging driver configure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1966889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966889] Re: docker-build containers do not have logging driver configure
Unfortunately for your use case, this is an intentional feature of `docker build` itself: https://github.com/moby/moby/blob/0a3336fd7d19f7114fce2ff849a8989ed33e2059/builder/dockerfile/internals.go#L377 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966889 Title: docker-build containers do not have logging driver configure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1966889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950751] Re: docker.io 20.10.x does not create sub-directories in /var/lib/docker on start (but does on restart)
In your second (working) example, I see you run "service docker stop"
before deleting the contents of "/var/lib/docker" but I do not see that
in your first example, which would definitely explain the behavior you
see ("service docker start" would be a no-op because Docker's already
running, and you've just yanked out all the data from underneath it, so
it's not very surprising that it sees errors trying to access said
data).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1950751
Title:
docker.io 20.10.x does not create sub-directories in /var/lib/docker
on start (but does on restart)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1950751/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942276] Re: docker 20.10.7-0ubuntu2 fails to start when installed inside Impish LXD container
After some discussion with mwhudson, I tried the following: - add proposed - install the libc6/libc-bin updates (which breaks a lot of stuff) - restart the container - stuff is working again - install docker.io (from proposed) - profit -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942276 Title: docker 20.10.7-0ubuntu2 fails to start when installed inside Impish LXD container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1942276/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942276] Re: docker 20.10.7-0ubuntu2 fails to start when installed inside Impish LXD container
I can reproduce, but I can even reproduce lots of failures by only upgrading "libc6" and "libc-bin" (which come in with "docker.io"), without Docker even installed or being installed. Lots of other services then try to restart and fail to do so, and "apt update" even starts failing to resolve DNS. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942276 Title: docker 20.10.7-0ubuntu2 fails to start when installed inside Impish LXD container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1942276/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897932] Re: systemd-repart not packaged
** Bug watch added: Debian Bug tracker #976959 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976959 ** Also affects: systemd (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976959 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897932 Title: systemd-repart not packaged To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1897932/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822632] Re: gosu: error while loading shared libraries: R_PPC64_ADDR16_HA reloc at 0x00000b69c5feaf58 for symbol `' out of range
This is kind of an old issue now, but it's still outstanding on both Bionic and Focal -- any chance it could get some love? It breaks our ability to build certain images on ppc64le (rabbitmq as a notable example). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822632 Title: gosu: error while loading shared libraries: R_PPC64_ADDR16_HA reloc at 0x0b69c5feaf58 for symbol `' out of range To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gosu/+bug/1822632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906959] Re: `apt purge` does not remove /var/lib/docker
Just to verify, I installed docker.io version 19.03.8-0ubuntu1.20.04.1, started up dockerd, verified /var/lib/docker got some content in it, and then stopped dockerd and ran "apt purge docker.io", and "/var/lib/docker" was properly emptied. It was not removed completely (in case it's a mount point or something similar), but there's no content in it (left as just an empty directory). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906959 Title: `apt purge` does not remove /var/lib/docker To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1906959/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906959] Re: `apt purge` does not remove /var/lib/docker
This confuses me, because this is already implemented? - https://git.launchpad.net/ubuntu/+source/docker.io/tree/debian/docker.io.prerm?h=applied/ubuntu/devel - https://git.launchpad.net/ubuntu/+source/docker.io/tree/debian/docker.io.postrm?h=applied/ubuntu/devel It was added ~four years ago in 1.11.2-0ubuntu6: docker.io (1.11.2-0ubuntu6) yakkety; urgency=medium ... - remove "/var/lib/docker" on purge ... -- Tianon Gravi Fri, 19 Aug 2016 10:15:14 -0700 It sounds like maybe there's a bug where this isn't working correctly in all cases? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906959 Title: `apt purge` does not remove /var/lib/docker To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1906959/+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
Aha, this sounds like it's probably the same root cause that led to https://github.com/docker/docker-ce-packaging/pull/508. -- 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 1871268] Re: Installation fails when "Install Third-Party Drivers" is selected
I think the core of this is fixed, but there's some situations still where it triggers -- here's a new reproducer that can still trigger it reliably with Docker (since I can't reproduce with the simplified steps in #31 anymore): ``` $ docker pull ubuntu:20.04 20.04: Pulling from library/ubuntu Digest: sha256:bc2f7250f69267c9c6b66d7b6a81a54d3878bb85f1ebb5f951c896d13e6ba537 Status: Image is up to date for ubuntu:20.04 docker.io/library/ubuntu:20.04 $ docker run --rm ubuntu:20.04 sh -c 'dpkg --add-architecture i386 && apt-get update -qq && apt-get install -y libc6:i386 libfontconfig1:i386 libgl1-mesa-dri:i386 libgl1-mesa-glx:i386' Reading package lists... Building dependency tree... Reading state information... The following additional packages will be installed: fontconfig-config fonts-dejavu-core gcc-10-base gcc-10-base:i386 libatomic1:i386 libbsd0:i386 libcrypt1:i386 libdrm-amdgpu1:i386 libdrm-common libdrm-intel1:i386 libdrm-nouveau2:i386 libdrm-radeon1:i386 libdrm2:i386 libedit2:i386 libelf1:i386 libexpat1:i386 libffi7:i386 libfreetype6:i386 libgcc-s1 libgcc-s1:i386 libgl1:i386 libglapi-mesa:i386 libglvnd0:i386 libglx-mesa0:i386 libglx0:i386 libidn2-0:i386 libllvm10:i386 libpciaccess0:i386 libpng16-16:i386 libsensors-config libsensors5:i386 libstdc++6 libstdc++6:i386 libtinfo6:i386 libunistring2:i386 libuuid1:i386 libvulkan1:i386 libwayland-client0:i386 libx11-6:i386 libx11-data libx11-xcb1:i386 libxau6:i386 libxcb-dri2-0:i386 libxcb-dri3-0:i386 libxcb-glx0:i386 libxcb-present0:i386 libxcb-randr0:i386 libxcb-sync1:i386 libxcb1:i386 libxdamage1:i386 libxdmcp6:i386 libxext6:i386 libxfixes3:i386 libxshmfence1:i386 libxxf86vm1:i386 libzstd1:i386 mesa-vulkan-drivers:i386 ucf uuid-runtime zlib1g zlib1g:i386 Suggested packages: glibc-doc:i386 locales:i386 pciutils:i386 lm-sensors lm-sensors:i386 The following NEW packages will be installed: fontconfig-config fonts-dejavu-core gcc-10-base:i386 libatomic1:i386 libbsd0:i386 libc6:i386 libcrypt1:i386 libdrm-amdgpu1:i386 libdrm-common libdrm-intel1:i386 libdrm-nouveau2:i386 libdrm-radeon1:i386 libdrm2:i386 libedit2:i386 libelf1:i386 libexpat1:i386 libffi7:i386 libfontconfig1:i386 libfreetype6:i386 libgcc-s1:i386 libgl1:i386 libgl1-mesa-dri:i386 libgl1-mesa-glx:i386 libglapi-mesa:i386 libglvnd0:i386 libglx-mesa0:i386 libglx0:i386 libidn2-0:i386 libllvm10:i386 libpciaccess0:i386 libpng16-16:i386 libsensors-config libsensors5:i386 libstdc++6:i386 libtinfo6:i386 libunistring2:i386 libuuid1:i386 libvulkan1:i386 libwayland-client0:i386 libx11-6:i386 libx11-data libx11-xcb1:i386 libxau6:i386 libxcb-dri2-0:i386 libxcb-dri3-0:i386 libxcb-glx0:i386 libxcb-present0:i386 libxcb-randr0:i386 libxcb-sync1:i386 libxcb1:i386 libxdamage1:i386 libxdmcp6:i386 libxext6:i386 libxfixes3:i386 libxshmfence1:i386 libxxf86vm1:i386 libzstd1:i386 mesa-vulkan-drivers:i386 ucf uuid-runtime zlib1g:i386 The following packages will be upgraded: gcc-10-base libgcc-s1 libstdc++6 zlib1g 4 upgraded, 61 newly installed, 0 to remove and 0 not upgraded. ... Processing triggers for libc-bin (2.31-0ubuntu9.1) ... E: Could not configure 'libc6:i386'. E: Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) ``` I'm certain that list can be made more specific, but I've tried the obvious packages and haven't had much luck in narrowing down much further. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871268 Title: Installation fails when "Install Third-Party Drivers" is selected To manage notifications about this bug go to: https://bugs.launchpad.net/glibc/+bug/1871268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871268] Re: Installation fails with Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'
I'm running into this building a Docker image that's "FROM ubuntu:20.04" and just trying to install libc6:i386. Here's the simplest reproducer I've come up with: ``` $ docker pull ubuntu:20.04 20.04: Pulling from library/ubuntu Digest: sha256:cbcf86d7781dbb3a6aa2bcea25403f6b0b443e20b9959165cf52d2cc9608e4b9 Status: Image is up to date for ubuntu:20.04 docker.io/library/ubuntu:20.04 $ docker run --rm ubuntu:20.04 sh -c 'dpkg --add-architecture i386 && apt-get update -qq && apt-get install -y libc6:i386' Reading package lists... Building dependency tree... Reading state information... The following additional packages will be installed: gcc-10-base:i386 libc6 libcrypt1:i386 libgcc-s1:i386 libidn2-0:i386 libunistring2:i386 Suggested packages: glibc-doc locales glibc-doc:i386 locales:i386 The following NEW packages will be installed: gcc-10-base:i386 libc6:i386 libcrypt1:i386 libgcc-s1:i386 libidn2-0:i386 libunistring2:i386 The following packages will be upgraded: libc6 1 upgraded, 6 newly installed, 0 to remove and 1 not upgraded. Need to get 5871 kB of archives. After this operation, 15.2 MB of additional disk space will be used. ... Processing triggers for libc-bin (2.31-0ubuntu9) ... E: Could not configure 'libc6:i386'. E: Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) ``` Looking at my GitHub Actions logs, it was working fine two days ago (Sep 21) and was broken starting yesterday (Sep 22), in case that helps narrow down which uploads might have caused the breakage. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871268 Title: Installation fails with Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1871268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869963] Re: Unable to install chromium-browser in docker
That's entirely fair, but in that case isn't going snap-only for "chromium-browser" a bit short-sighted, given the constraints on running snaps? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869963 Title: Unable to install chromium-browser in docker To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1869963/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879473] Re: hundreds of snapshots created by docker zfs lead to zsys timeout
The "zfs" graph driver is part of Docker itself (https://github.com/moby/moby/tree/89382f2f20745b9e63bed6c066f104980dff4396/daemon/graphdriver/zfs), so https://github.com/moby/moby/issues would be the appropriate place to file an issue (or enhancement request) against it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879473 Title: hundreds of snapshots created by docker zfs lead to zsys timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1879473/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879473] Re: hundreds of snapshots created by docker zfs lead to zsys timeout
Has this been reported upstream? The fix (in postinst) is large enough that it seems like something upstream should at least be aware of, and is probably something they should implement a fix for as well. Do you think it's something that could/should be fixed in "dockerd" itself? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879473 Title: hundreds of snapshots created by docker zfs lead to zsys timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1879473/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814896] Re: upgrade Docker snap to 18.09.1
18.09.9 has been in stable for a while now, and 19.03.8 has been in beta for a short time (hopefully stable soon). :) ** Changed in: docker (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814896 Title: upgrade Docker snap to 18.09.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker/+bug/1814896/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875882] Re: debconf attempts interactive configuration; breaks Docker image builds
** Also affects: debconf (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/1875882 Title: debconf attempts interactive configuration; breaks Docker image builds To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1875882/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858248] Re: /lib/systemd/system/docker.service lacks EnvironmentFile
The upstream-supported method of accomplishing this is via a systemd drop-in which overrides ExecStart. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858248 Title: /lib/systemd/system/docker.service lacks EnvironmentFile To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1858248/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852720] Re: docker snap suddenly installed by itself
Thanks for testing and confirming! Fix is now released to the stable channel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852720 Title: docker snap suddenly installed by itself To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1852720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852720] Re: docker snap suddenly installed by itself
My fix finished building and uploading into the edge channel, so if folks could test it from either edge or beta (I'd suggest beta, but your choice), that would be helpful. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852720 Title: docker snap suddenly installed by itself To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1852720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852720] Re: docker snap suddenly installed by itself
At least for the "Docker fails to run containers and fill syslog" half of this, I've reproduced in https://forum.snapcraft.io/t/docker- snap-18-09-9-error/14171/5 and have a fix committed waiting for Launchpad to build so I can rush it through the channels ASAP. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852720 Title: docker snap suddenly installed by itself To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1852720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851353] Re: docker.io, but not podman?
This is definitely not the appropriate place for this to be filed (because "src:podman" not existing is definitely not a *Docker* bug). What would be more appropriate would be to take a look at https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages. ** Changed in: docker.io (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851353 Title: docker.io, but not podman? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1851353/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834997] Re: Docker snap is stuck. Cannot use or remove
>From the Docker perspective, it sounds like there's a process stuck somewhere. I'd recommend checking the system for any leftover "docker" processes (dockerd, containerd, shim processes, etc) via something like "ps faux | grep docker" (and/or "containerd", "runc", "shim", etc). The "dockerd" service logs might also have some clues, and I believe "journalctl -u snap.docker.dockerd.service" is the right way to access those in Snappy? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834997 Title: Docker snap is stuck. Cannot use or remove To manage notifications about this bug go to: https://bugs.launchpad.net/docker/+bug/1834997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822632] [NEW] gosu: error while loading shared libraries: R_PPC64_ADDR16_HA reloc at 0x00000b69c5feaf58 for symbol `' out of range
Public bug reported: After installing "gosu" on Bionic on ppc64el, attempts to run the resulting "gosu" binary result in the following error message: gosu: error while loading shared libraries: R_PPC64_ADDR16_HA reloc at 0x0b41bcc7af58 for symbol `' out of range I spoke briefly with mwhudson about it (recalling he might've dealt with similar issues previously) and he suggested it probably needs a rebuild and asked me to file a bug. :) (Something something PIC something something PIE something something Go toolchain.) ** Affects: gosu (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/1822632 Title: gosu: error while loading shared libraries: R_PPC64_ADDR16_HA reloc at 0x0b69c5feaf58 for symbol `' out of range To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gosu/+bug/1822632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820278] Re: Incorrect DNS (resolv.conf) setup inside docker images
Anything useful in Docker's daemon logs? As a workaround you should be able to set --dns on your container or adjust /etc/docker/daemon.json to adjust that setting more permanently. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820278 Title: Incorrect DNS (resolv.conf) setup inside docker images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1820278/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820278] Re: Incorrect DNS (resolv.conf) setup inside docker images
Have you tried restarting the Docker daemon? (IIRC it caches the DNS settings during startup) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820278 Title: Incorrect DNS (resolv.conf) setup inside docker images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1820278/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1808266] Re: Docker daemon drops all bound ports, recovers them after long docker ps
Yep, that would be socket activation; I'd recommend explicitly enabling "docker.service" so it starts on boot as expected. đź‘Ť -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1808266 Title: Docker daemon drops all bound ports, recovers them after long docker ps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1808266/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808266] Re: Docker daemon drops all bound ports, recovers them after long docker ps
This sounds to me like Docker restarted for some reason -- do you have some kind of automated update process in place? If it's unattended, it could potentially restart Docker, but the logs you've provided include a host reboot too, which would definitely look like this externally. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1808266 Title: Docker daemon drops all bound ports, recovers them after long docker ps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1808266/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1784602] Re: No option to configure docker.io for restart on package upgrade
Proposed patch attached -- I've tested that this: 1. does not prompt on initial install (but does start the daemon) 2. does prompt on every reinstall / upgrade (if the daemon is running) 3. does prompt during "dpkg-reconfigure docker.io" (but does _not_ [re]start the daemon) 4. works properly with DEBIAN_FRONTEND=noninteractive -- user's previous/stored answer to the question automatically applies with no prompt ** Patch added: "prompt-during-reconfigure.patch" https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1784602/+attachment/5170142/+files/prompt-during-reconfigure.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1784602 Title: No option to configure docker.io for restart on package upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1784602/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1784602] Re: No option to configure docker.io for restart on package upgrade
I can confirm this behavior -- there's a bug in the postinst script where it makes sure we don't restart the daemon during "dpkg- reconfigure" (since that should only happen during install/upgrade), but instead it also stops us from prompting during "dpkg-reconfigure", which isn't right. I think we need to move the check for "dpkg-reconfigure" slightly further inward to only apply to the actual restart event so that we still prompt (and can thus configure non-interactive installs appropriately). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1784602 Title: No option to configure docker.io for restart on package upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1784602/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1699913] Re: /var/lib/apt/lists has content in partner-images/Docker tarballs, which becomes stale quickly
++ Absolutely agree that having "apt-get install" auto-update stale indexes would be ideal (or even a "--update" flag to install for combining them); looks like that discussion is over in bug 1709603. :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1699913 Title: /var/lib/apt/lists has content in partner-images/Docker tarballs, which becomes stale quickly To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1699913/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1755250] Re: backport statx syscall whitelist fix
Looking into this deeper -- applying this patch for bionic will have net-zero effect, given this comment: https://github.com/moby/moby/pull/36417#issuecomment-369266565 For this patch to do anything, "libseccomp" needs to be at least version 2.3.3, and bionic is only at 2.3.1 (so the added line would essentially be ignored and you'd still get EPERM). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755250 Title: backport statx syscall whitelist fix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1755250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1732368] Re: upgrade to 17.03.2-ce in 16.04+
> The reason this is being done as a debconf question is because neither option is good. And *since* we are forced to ask the user to pick their poison, I consider it insufficient to ask this question only once. The question should by default be re-asked, at each package upgrade, so that the user has an opportunity to make the decision that is correct for them at that moment. > In addition, the current default for the debconf question is "true"; so by default, which includes on non-interactive upgrades (unattended upgrades or the like), the behavior the user gets here is that the service is restarted, stopping any un-supervised containers. If the docker.io package is not able to detect whether all running containers will be automatically restarted, then if this is to be a supported use case at all, the default should be to not restart: because it is less disruptive to have the docker service become unavailable, than to have the docker containers become unavailable. Fair enough, will update Git and poke Michael when it's ready (thanks for noting the exact pattern we ought to be using to accomplish this). :) > "reconfigure" is not a valid argument to a postinst script. (And dpkg- reconfigure does not invoke it this way - it invokes it as 'postinst configure'.) So the first part of this test is always true and can be omitted. I included that because I read on the lists that it was intended to be supported _eventually_, but I guess that was long enough ago (and the transition wouldn't be fun to implement across the archive) that it's probably safe to ignore that ever happened; fair enough. O:) > And the check for status is not consistent with expected behavior of packages: upgrading the package should normally start the service even if it was currently not running, unless the administrator has explicitly disabled it through policy-rc.d. So, this block of code is _only_ responsible for performing the daemon restart, hence why this bit was included. Starting the daemon happens in the following block. To put it another way, if Docker isn't running, there's not really a good reason to even prompt the user whether we're OK to restart it -- we should just fire it up. Would it make more sense to have this block just stop the daemon instead and let the following block start it up? > This code includes a check for "$shouldStartRestart"; but this is the code to start the daemon on package initial installation, and the debconf question doesn't ask about starting, only about restarting. So I think this check shouldn't be there. The "$shouldStartRestart" variable basically amounts to "Are we running this script because of package install or because of 'dpkg- reconfigure'?" -- if the user is simply running "dpkg-reconfigure", I don't think it's appropriate or necessary for us to fire up the Docker daemon (or bother restarting it -- we only care about doing that when upgrading or installing the package). Since we're going to ditch the check for `[ "$1" != 'reconfigure' ]`, we can just use "$DEBCONF_RECONFIGURE" which will make this more clear. So to summarize, the current code, as written, will restart the daemon based on the user's input, but only during package install/upgrade (not during "dpkg-reconfigure"), and if the daemon isn't running, will start it up during package install/upgrade (also not during "dpkg- reconfigure"). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1732368 Title: upgrade to 17.03.2-ce in 16.04+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1732368/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754562] Re: Already created docker group prevents package docker.io 1.13.1-0ubuntu1~16.04.2 install
I'm guessing you added the group as a non-system group? (resulting in "addgroup: The group `docker' already exists and is not a system group. Exiting.") I think it would probably be sane to add a check similar to the one Docker itself uses (namely whether "/etc/group" includes a line that starts with "docker:" -- ie, not using "getent group" since Docker parses the file directly). something like: | if ! grep -q '^docker:' /etc/group 2>/dev/null; then | addgroup --system docker | fi --- See also: https://github.com/moby/moby/blob/3a633a712c8bbb863fe7e57ec132dd87a9c4eff7/daemon/listeners/group_unix.go#L20 https://github.com/opencontainers/runc/blob/69663f0bd4b60df09991c08812a60108003fa340/libcontainer/user/lookup_unix.go#L15 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754562 Title: Already created docker group prevents package docker.io 1.13.1-0ubuntu1~16.04.2 install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1754562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755250] Re: backport statx syscall whitelist fix
Indeed, looks like this fix isn't in a released version at all yet (likely to be in 18.04). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755250 Title: backport statx syscall whitelist fix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1755250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1751226] Re: purging docker.io fails
*** This bug is a duplicate of bug 1744599 *** https://bugs.launchpad.net/bugs/1744599 ** This bug has been marked a duplicate of bug 1744599 package docker.io (not installed) failed to install/upgrade: subprocess installed post-removal script returned error exit status 127 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1751226 Title: purging docker.io fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1751226/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1744599] Re: package docker.io (not installed) failed to install/upgrade: subprocess installed post-removal script returned error exit status 127
This was fixed upstream in 17.04+ (https://github.com/docker/docker/pull/30519) -- I could've sworn we backported the patch, but apparently not! (I'll go work on getting that applied now) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1744599 Title: package docker.io (not installed) failed to install/upgrade: subprocess installed post-removal script returned error exit status 127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1744599/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1711735] Re: source.list for armhf includes trusty-security which does not exist for arm
This is still causing quite a _lot_ of downstream pain -- any chance it could be re-prioritized? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1711735 Title: source.list for armhf includes trusty-security which does not exist for arm To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1711735/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1711735] Re: source.list for armhf includes trusty-security which does not exist for arm
He means simply removing "trusty + armhf" for the "ros" and/or "gazebo" images, I believe (not for the "ubuntu" image). The harm this causes is that "apt-get update" fails, which causes the whole "docker build" to fail. Here's an example from ppc64el: W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/trusty-security/main/binary-ppc64el/Packages 404 Not Found [IP: 91.189.88.152 80] W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/trusty-security/restricted/binary-ppc64el/Packages 404 Not Found [IP: 91.189.88.152 80] W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/trusty-security/universe/binary-ppc64el/Packages 404 Not Found [IP: 91.189.88.152 80] W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/trusty-security/multiverse/binary-ppc64el/Packages 404 Not Found [IP: 91.189.88.152 80] E: Some index files failed to download. They have been ignored, or old ones used instead. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1711735 Title: source.list for armhf includes trusty-security which does not exist for arm To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1711735/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1683450] Re: hello-world doesn't work at i386
The "hello-world" image is a 64bit image; you'll need something 32bit to run on that system (like i386/hello-world -- https://hub.docker.com/r/i386/hello-world/). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1683450 Title: hello-world doesn't work at i386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1683450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506337] Re: No Internet inside Docker containers
This was filed against the wrong Docker package (talks about containers); didn't verify whether it's valid but wanted to get it pointed at the right package anyhow. ** Package changed: docker (Ubuntu) => docker.io (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506337 Title: No Internet inside Docker containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1506337/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1657646] Re: VG/LV are not available in /dev/mapper/ after reboot
** Package changed: docker (Ubuntu) => docker.io (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1657646 Title: VG/LV are not available in /dev/mapper/ after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1657646/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652270] Re: Could not boot into RPi3 with kernel 4.4.0-1038-raspi2
I think it's probably more likely that this is related to the changes to the dtb address over in #1636838 (although after hacking at it for a while trying to make those changes ad-hoc for verification, I wasn't able to confirm that hunch for sure). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1652270 Title: Could not boot into RPi3 with kernel 4.4.0-1038-raspi2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1652270/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655906] Re: Please upgrade docker.io to latest 1.12.6
Looks like LP doesn't want me to assign mwhudson. :) (only myself or one of my teams) So, uh, these are all pushed in Git, ready for review/sponsorship (I've pushed builds to the PPA and tested in zesty successfully). ** Also affects: containerd (Ubuntu) Importance: Undecided Status: New ** Changed in: containerd (Ubuntu) Status: New => In Progress ** Changed in: containerd (Ubuntu) Assignee: (unassigned) => Tianon Gravi (tianon) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1655906 Title: Please upgrade docker.io to latest 1.12.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd/+bug/1655906/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655906] Re: Please upgrade docker.io to latest 1.12.6
** Also affects: runc (Ubuntu) Importance: Undecided Status: New ** Changed in: runc (Ubuntu) Assignee: (unassigned) => Tianon Gravi (tianon) ** Changed in: runc (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1655906 Title: Please upgrade docker.io to latest 1.12.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1655906/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652270] Re: Could not boot into RPi3 with kernel 4.4.0-1038-raspi2
I got the breaking-update automatically via unattended-upgrades -- no human intervention of any kind. Simply rebooted the RPi3 after the holidays and it failed to come back up. To fix it, I used "qemu-user-static"'s ARM emulation to get a chroot into the SD card's system on my laptop, and then I did "apt-get purge linux-image-4.4.0-1038-raspi2 linux-headers-4.4.0-1038-raspi2 linux- raspi2-headers-4.4.0-1038" so that it'd force the older kernel to be the latest (make sure you do in fact have the older kernel package installed -- "dpkg -l | grep linux-image"). That also purged the "linux-image-raspi2" metapackage, so I'm not likely to get any further automatic kernel updates (which really is a bad thing, given that they're likely to contain security fixes), but until this is fixed, I'm not willing to risk it (need the box to be up and running more urgently). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1652270 Title: Could not boot into RPi3 with kernel 4.4.0-1038-raspi2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1652270/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1644230] Re: Can't run any container: shim error: open pid: no such file or directory
Interesting. I've seen some success in situations like this from simply restarting the Docker daemon -- mind giving that a shot? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1644230 Title: Can't run any container: shim error: open pid: no such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1644230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1645992] Re: package docker.io 1.12.1-0ubuntu13~16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Is "JournalErrors.txt" the output of "journalctl" for the service? I don't see anything useful in there regarding Docker startup output. :/ Has this machine had Docker installed previously, or is this a clean install? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1645992 Title: package docker.io 1.12.1-0ubuntu13~16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1645992/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1639407] Re: Docker not built with seccomp
This is definitely a real issue, and it wasn't intentional -- I've got a fix in progress, but it needs to happen in both the runc and the docker.io packages. ** Changed in: docker.io (Ubuntu) Status: New => Confirmed ** Also affects: runc (Ubuntu) Importance: Undecided Status: New ** Changed in: runc (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1639407 Title: Docker not built with seccomp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1639407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1631230] Re: auplink spam in docker unit log
Yeah, I think in Ubuntu changing that to "Recommends" is sensible. - Tianon -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1631230 Title: auplink spam in docker unit log To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1631230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1631230] [NEW] auplink spam in docker unit log
It should already be in either recommends or suggests (can't remember which). IMO "depends" is inappropriate because it's only required if your kernel both supports AUFS and it's configured or chosen as your graph driver. BTRFS, overlayfs, and even ZFS are also supported, for example. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1631230 Title: auplink spam in docker unit log To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1631230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1628053] Re: package docker.io 1.12.1-0ubuntu13~16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
>From what I've seen in the past, this is almost always indicative of daemon startup errors (either "/var/log/docker.log" or "journalctl -u docker.service" depending on init system), which are _usually_ related to graph drivers (such as the AUFS module failing to load for some reason, or a mix of several driver's states and nothing to disambiguate which is preferred, for example). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1628053 Title: package docker.io 1.12.1-0ubuntu13~16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1628053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1622407] Re: package docker.io 1.11.2-0ubuntu5~16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
The important bits there are these: Sep 30 16:42:55 einstein docker[5009]: time="2016-09-30T16:42:55.781784363+02:00" level=error msg="[graphdriver] prior storage driver \"aufs\" failed: driver not supported" Sep 30 16:42:55 einstein docker[5009]: time="2016-09-30T16:42:55.781825992+02:00" level=fatal msg="Error starting daemon: error initializing graphdriver: driver not supported" Did you switch to a kernel which doesn't include AUFS support? For the official kernels (such as "linux-image-4.4.0-21-generic"), the AUFS module is contained within the "extra" package (ie "linux-image-extra-4.4.0-21-generic"). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1622407 Title: package docker.io 1.11.2-0ubuntu5~16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1622407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1609087] Re: Ubuntu docker images should create /run/container_type & /run/systemd/container
https://github.com/tianon/docker-brew-ubuntu-core/pull/64 is relevant here. :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1609087 Title: Ubuntu docker images should create /run/container_type & /run/systemd/container To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1609087/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1567090] Re: Cannot create more than ~2500 containers due to golang setMaxThreads param
This is fixed now that we've got "TasksMax=infinity" in our systemd service file, right? (The commit referenced above is also included in all the 1.11 releases, so either way we should be fixed here.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1567090 Title: Cannot create more than ~2500 containers due to golang setMaxThreads param To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1567090/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1469204] Re: /etc/default/docker format is wrong for systemd service
Yeah, I agree and want to get there, but I figured just dropping it straight away would be doing our users a disservice (especially since it might not be obvious right away that it's not being used anymore). For example, if a user has "--bip=..." set in DOCKER_OPTS in that file, then dropping the sourcing of it outright wouldn't cause the service to fail to start or anything, and it actually wouldn't change anything for the running system until the next reboot (at which time, Docker would revert back to choosing its own IP range, which will be a nasty surprise for said operator). :( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1469204 Title: /etc/default/docker format is wrong for systemd service To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1469204/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1469204] Re: /etc/default/docker format is wrong for systemd service
https://anonscm.debian.org/cgit/docker/docker.io.git/commit/?id=0bc5ad426c84804c939804e33247140ff2636991 is the compromise I've applied in Debian recently (replacing the file's contents with a long-form note pointing our users to the upstream- recommended alternatives, which should invoke dpkg's configuration file merge and also not break existing users right away). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1469204 Title: /etc/default/docker format is wrong for systemd service To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1469204/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1603244] [NEW] docker - Cannot start container
This appears to be because "hello-world" is an amd64 image and you appear to be on an s390x system -- can you try "s390x/hello-world" instead? :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1603244 Title: docker - Cannot start container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1603244/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1602243] Re: [FEAT 16.10] Upgrade Docker to newest version 1.12
IMO it's also worth noting that 1.12.0 isn't GA yet -- upstream is still doing release candidates (currently at rc4), and the _current_ planned date for 1.12.0 is July 28th (although it used to be the 14th, so there's nothing to say it won't change again, especially if more issues manifest during the RCs). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1602243 Title: [FEAT 16.10] Upgrade Docker to newest version 1.12 To manage notifications about this bug go to: https://bugs.launchpad.net/docker.io/+bug/1602243/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1581720] Re: Raspberry Pi 3 64-bit kernel
I think https://github.com/raspberrypi/firmware/issues/550 has some relevant information, especially https://github.com/raspberrypi/firmware/issues/550#issuecomment-190780010 (RPi Foundation is not working on arm64) and https://github.com/raspberrypi/firmware/issues/550#issuecomment-197452521 (which points to some community members that are making good progress). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1581720 Title: Raspberry Pi 3 64-bit kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1581720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1563184] Re: Chromium-browser armhf crashes with "InitializeSandbox() called with multiple threads in process gpu-process"
The debdiff from xenial to trusty (attached) doesn't appear terribly interesting. :( ** Patch added: "xenial-to-trusty.debdiff" https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1563184/+attachment/4665562/+files/xenial-to-trusty.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1563184 Title: Chromium-browser armhf crashes with "InitializeSandbox() called with multiple threads in process gpu-process" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1563184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1563184] Re: Chromium-browser armhf crashes with "InitializeSandbox() called with multiple threads in process gpu-process"
Hit the same issue on my own new Raspberry Pi 3 running Ubuntu Xenial (installed via http://www.finnie.org/software/raspberrypi/ubuntu- rpi3/ubuntu-16.04-preinstalled-server-armhf+raspi3.img.xz linked from https://wiki.ubuntu.com/ARM/RaspberryPi). I managed to get a little bit further by installing the "chromium- browser" package from "trusty" (which appears to be the same underlying Chromium version backported; more exactly, package version "49.0.2623.108-0ubuntu0.14.04.1.1113"). That at least lets the browser come up, but all the pages crash (as opposed to the entire browser crashing, like the xenial version does). When I add "--no-sandbox" (which is inherently dangerous and adds an appropriate warning to the UI every time you launch chrome), I can get much further and actually have a functional Chromium instance (but using "--no-sandbox" is obviously pretty far from ideal). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1563184 Title: Chromium-browser armhf crashes with "InitializeSandbox() called with multiple threads in process gpu-process" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1563184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1576419] Re: autopkgtests kill ssh
I ran it locally with a 4GB VM and managed to get through all the tests without sshd dying. :( (obviously we've got some failures that we'll need to figure out, but probably only worth figuring out the failures if we can figure out why sshd is getting killed D: ) OOPS: 192 passed, 120 skipped, 894 FAILED, 6 MISSED --- FAIL: Test (1244.15s) FAIL coverage: 47.5% of statements exit status 1 FAIL _/tmp/adt-run.Y8vt5w/build.Xj2/real-tree/integration-cli 1244.578s ---> Making bundle: .integration-daemon-stop (in bundles/1.10.3/test-integration-cli) + cat bundles/1.10.3/test-integration-cli/docker.pid kill 21965 adt-run [16:35:41]: test integration: ---] adt-run [16:35:42]: test integration: - - - - - - - - - - results - - - - - - - - - - integration FAIL non-zero exit status 1 adt-run [16:35:42]: summary integration FAIL non-zero exit status 1 qemu-system-x86_64: terminating on signal 15 from pid 6 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1576419 Title: autopkgtests kill ssh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1576419/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1576419] Re: autopkgtests kill ssh
This sounds suspiciously like OOM killing sshd, not Docker's tests directly -- I know the integration tests used to require anywhere from 1 to 4 GB of RAM, and I imagine that's probably still the case. :( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1576419 Title: autopkgtests kill ssh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1576419/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1574904] Re: Docker compiled with wrong version of Go
Applying https://github.com/docker/docker/pull/22000 is another option worth considering. The patch isn't ideal (and upstream currently has no interest in applying it), but it does do the job. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1574904 Title: Docker compiled with wrong version of Go To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1574904/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1572912] Re: package docker.io 1.10.3-0ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
That output is still cut off, but does show the problem: time="2016-04-21T12:26:54.837949976+01:00" level=fatal msg="Error starting daemon: error initializing graphdriver: \"/var/lib/docker\" contains other graphdrivers: d We're missing the end of this log line which would tell us exactly which other graph driver your machine has used previously that it doesn't think it can use now -- the simplest fix would be to just "rm -rf /var/lib/docker", but only if you don't have anything important you've been using Docker for. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1572912 Title: package docker.io 1.10.3-0ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1572912/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1572912] Re: package docker.io 1.10.3-0ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
That output looks like the actual error message is getting cut off -- "journalctl -u docker.service | tail" might give us a slightly more useful indication (at the very least, hopefully the full error message from the daemon). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1572912 Title: package docker.io 1.10.3-0ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1572912/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1469204] Re: /etc/default/docker format is wrong for systemd service
IMO we should just remove the patch we add that makes it apply; systemd drop in files are the way systemd upstream recommends configuring startup parameters like this, which is why upstream doesn't include the EnvironmentFile directive that we've patched in. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1469204 Title: /etc/default/docker format is wrong for systemd service To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1469204/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1503674] [NEW] depends on iptables instead of nftables
I think this is an upstream bug because last I checked Docker shells out to iptables directly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1503674 Title: depends on iptables instead of nftables To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1503674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1392094] Re: golang is unavailable for arm64
The current patch seems like it comes more from https://github.com/docker/docker/pull/10569 than from the referenced https://github.com/docker/docker/pull/10665, and basically this same diff has been rejected upstream multiple times. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1392094 Title: golang is unavailable for arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1392094/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1392094] Re: golang is unavailable for arm64
Even the current patch headers are misleading: > Description: Add gccgo build support for Power > This patch is based on one that has been accepted upstream > in trunk with some minor additions to deal with the way > that the dh-golang helper works in Debian/Ubuntu. > Origin: https://github.com/docker/docker/pull/10665 The "Description" claims this patch is actually based on something that exists upstream, but nothing like that patch exists upstream, and the "Origin" linked is a very different patch (and was merged as part of the work towards getting GCCGO upstream). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1392094 Title: golang is unavailable for arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1392094/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1392094] Re: golang is unavailable for arm64
I'm actually really concerned by this change (speaking as both a Debian maintainer on the package, and as the maintainer of the build scripts upstream). We're actively working upstream on getting proper first- class gccgo compilation support into Docker's build system (https://github.com/docker/docker/issues/9207 for the tracker upstream), but one of the things we've noticed is that just because it doesn't FTBFS doesn't mean it actually works. Have you run it against the upstream integration tests to at least get an initial verification that the daemon works as expected? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1392094 Title: golang is unavailable for arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1392094/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1396760] Re: ca-certificates-java doesn't create /etc/ssl/certs/java/cacerts
https://bugs.debian.org/775775 :D (more reproducing, and a patch) ** Bug watch added: Debian Bug tracker #775775 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775775 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1396760 Title: ca-certificates-java doesn't create /etc/ssl/certs/java/cacerts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates-java/+bug/1396760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1396760] Re: ca-certificates-java doesn't create /etc/ssl/certs/java/cacerts
Has this also been reported upstream in Debian? I can't find anything related in the BTS. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1396760 Title: ca-certificates-java doesn't create /etc/ssl/certs/java/cacerts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates-java/+bug/1396760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1407408] Re: please merge docker.io from debian
Paul can't take all the credit for that being missing. :) I left it out because we leave out "dh_auto_build" in our "override_dh_auto_build", so I figured whatever future behavior "dh_auto_clean" might include we probably want to choose to include here manually, since the "Docker build system" likely won't ever be one debhelper automatically detects. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1407408 Title: please merge docker.io from debian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1407408/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1366509] Re: "exec format error" with "docker run ubuntu" right after installation
I agree completely, but upstream isn't planning to change that in the near future (especially since this particular configuration is not only unsupported, but the Debian/Ubuntu package includes a 100% unapproved-by-upstream patch to make it even possible). _Maybe_ today's Microsoft news will help upstream make the necessary changes to support different platforms with a better/smoother UX, but only time will tell. For now, this issue is definitely very firmly in the not-a-bug category (especially as far as the Ubuntu packaging is concerned). The argument could actually be made that the Debian/Ubuntu package should instead drop the unapproved patch that makes this particular configuration possible, but that's certainly not going to be a popular choice with the people currently using and enjoying it with their own home-grown images. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1366509 Title: error message when running images of the wrong arch can be considered confusing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1366509/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1366509] Re: "exec format error" with "docker run ubuntu" right after installation
As was noted on the upstream issue, this is working as designed. You cannot run a 64bit image on a 32bit host. Also, upstream does not officially support 32bit hosts, so you will need to use something like debootstrap to create your own. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1366509 Title: "exec format error" with "docker run ubuntu" right after installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1366509/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1369927] Re: [FFe] Sync docker.io 1.2.0 from Debian unstable
Yes ♥, - Tianon On 16 Sep 2014 10:31, "Paul Tagliamonte" wrote: > Nice! :D > > On Tue, Sep 16, 2014 at 12:13 PM, James Page > wrote: > > Thanks Iain > > > > Sync'ing away! > > > > -- > > You received this bug notification because you are a member of Docker > > Ubuntu Maintainers, which is subscribed to docker.io in Ubuntu. > > https://bugs.launchpad.net/bugs/1369927 > > > > Title: > > [FFe] Sync docker.io 1.2.0 from Debian unstable > > > > Status in “docker.io” package in Ubuntu: > > Confirmed > > Status in “golang-context” package in Ubuntu: > > Confirmed > > > > Bug description: > > 1.2.0 is the latest stable release from upstream; Tianon, Paul and > > Andrew have completed packaging updates and uploaded to Debian > > unstable. > > > > I've pulled the required updates into https://launchpad.net/~james- > > page/+archive/ubuntu/docker1.2 for Utopic. > > > > This update will require syncs of the following NEW packages: > > > > go-md2man > > golang-blackfriday > > golang-go-patricia > > > > and an updates to: > > > > golang-context (bump to 0.0~git20140604.1.14f550f-1) > > docker.io (bump to 1.2.0) > > > > I've tested upgrades and functionality using the PPA built packages as > > detail above. > > > > See: > > > > https://github.com/docker/docker/blob/master/CHANGELOG.md > > > > for the full changelog of updates since 1.0.1 as currently in Utopic. > > > > To manage notifications about this bug go to: > > > https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1369927/+subscriptions > > > -- > All programmers are playwrights, and all computers are lousy actors. > > #define sizeof(x) rand() > :wq > > -- > You received this bug notification because you are a member of Docker > Ubuntu Maintainers, which is subscribed to docker.io in Ubuntu. > Matching subscriptions: docker.io > https://bugs.launchpad.net/bugs/1369927 > > Title: > [FFe] Sync docker.io 1.2.0 from Debian unstable > > Status in “docker.io” package in Ubuntu: > Confirmed > Status in “golang-context” package in Ubuntu: > Confirmed > > Bug description: > 1.2.0 is the latest stable release from upstream; Tianon, Paul and > Andrew have completed packaging updates and uploaded to Debian > unstable. > > I've pulled the required updates into https://launchpad.net/~james- > page/+archive/ubuntu/docker1.2 for Utopic. > > This update will require syncs of the following NEW packages: > > go-md2man > golang-blackfriday > golang-go-patricia > > and an updates to: > > golang-context (bump to 0.0~git20140604.1.14f550f-1) > docker.io (bump to 1.2.0) > > I've tested upgrades and functionality using the PPA built packages as > detail above. > > See: > > https://github.com/docker/docker/blob/master/CHANGELOG.md > > for the full changelog of updates since 1.0.1 as currently in Utopic. > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1369927/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1369927 Title: [FFe] Sync docker.io 1.2.0 from Debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1369927/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1362423] Re: docker.io inspect shows docker pid as 0
This would probably be good to report upstream. It might also be wise (and they'll request it upstream) to test it against 1.2.0 (or at least 1.0.1, which was pushed into utopic and is in trusty-updates too). Paul and I have also been playing with nightly builds of the docker.io package at https://launchpad.net/~docker-maint/+archive/ubuntu/testing which is an option if you want to test against roughly upstream master. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1362423 Title: docker.io inspect shows docker pid as 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1362423/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1366509] Re: "exec format error" with "docker run ubuntu" right after installation
You're on a 32bit system (i386) and trying to run a 64bit image (amd64). Systems that aren't 64bit are officially unsupported upstream, so to use one, you'll have to make your own images (including the base images), or find some that someone else has made with the appropriate architecture. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1366509 Title: "exec format error" with "docker run ubuntu" right after installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1366509/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1353923] Re: Installing Docker Breaks KVM
Just to note, this was also reported upstream at https://github.com/docker/docker/issues/7462 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1353923 Title: Installing Docker Breaks KVM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1353923/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1309288] Re: docker.io requires apparmor but package does not depend on it
Paul: we've got the dh_gencontrol stuff in our Git repo that adds apparmor to Recommends for Ubuntu - couldn't we at least start by backporting that one fix while the deps for a newer Docker version get sorted out (Bug #1338768)? (For reference, it's commit 01e64d44435c3ce83c0914074f9851b8c875c41d that adds this: http://anonscm.debian.org/cgit/docker/docker.io.git/commit/?id=01e64d44435c3ce83c0914074f9851b8c875c41d) This would need to be against our 0.9.1~dfsg1-2 release for now, right? If you think it'd be worthwhile, I'm happy to work up a branch for you to review that includes this fix and maybe any others we can make without our deps being bumped yet. Just say the word, boss! :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1309288 Title: docker.io requires apparmor but package does not depend on it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1309288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
