On Fri, Feb 16, 2018 at 08:15:35PM +0100, Julian Andres Klode wrote: > > I think the network-online.target is the better thing to key on. > > I think we should just grep the apt output and retry if it fails with > connection error messages.
The problem is a general one though. It's not specific to apt. Any time we use automation on a container or VM, we need to wait until it's finished booting. In uvtool this is what "uvt-kvm wait" provides, which currently waits for upstart runlevel 2 or systemd runlevel 5 and then asks cloud-init (since a script might also have asked cloud-init to do things it expects done when the container is "ready"). Of course that's cloud-init specific. The script may need fixing, but Ubuntu should agree upon a general answer to the common question. Even if the answer provides multiple specified points if multiple points in time are appropriate to solve different problems. So, to me, retrying apt is a hacky workaround. Robie
signature.asc
Description: PGP signature
-- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel