auplink spam in docker unit log

Bug #1631230 reported by Robert Collins
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
docker.io (Ubuntu)
Triaged
Undecided
Unassigned

Bug Description

Oct 06 14:48:13 linux-dev docker[1317]: time="2016-10-06T14:48:13.909019154+13:00" level=error msg="Couldn't run auplink before unmount /var/lib/docker/tmp/docker-aufs-union929083141: exec: \"auplink\": executable file not found in $PATH"
Oct 06 14:48:29 linux-dev docker[1317]: time="2016-10-06T14:48:29.216164082+13:00" level=error msg="Couldn't run auplink before unmount /var/lib/docker/aufs/mnt/6d15156cb4338d7264b7cb3d9404c99c860b897381837eaa498813e1b9ffc710-init: exec: \"auplink\": executable file not found in $PATH"

If this is harmless, it would be good to stop docker trying to run it. If its not, please depend on auplink so that it is installed automatically!

Revision history for this message
Tianon Gravi (tianon) wrote : 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.

Revision history for this message
Robert Collins (lifeless) wrote :

It is in suggests. This means that the default behaviour - the happy path - for users is poor. Ubuntu's kernels support aufs, and aufs is the default graph driver.

At a minimum I'd suggest recommends.

But aufs-tools is a) tiny - Installed-Size: 228 and b) has no further deps (other than libc) - so while you're abstractly correct its a correctness that isn't IMO helpful.

Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

I'd agree that a recommends wouldn't hurt in that case.
Especially since it would not be a component mismatch - both are in universe.

@Tianon/Mwhudson what do you think?

Revision history for this message
Michael Hudson-Doyle (mwhudson) wrote : Re: [Bug 1631230] Re: auplink spam in docker unit log

Recommends makes sense to me I think.

On 11 October 2016 at 01:54, ChristianEhrhardt <email address hidden>
wrote:

> I'd agree that a recommends wouldn't hurt in that case.
> Especially since it would not be a component mismatch - both are in
> universe.
>
> @Tianon/Mwhudson what do you think?
>
> --
> You received this bug notification because you are subscribed to
> docker.io in 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
>

Revision history for this message
Tianon Gravi (tianon) wrote :

Yeah, I think in Ubuntu changing that to "Recommends" is sensible.

- Tianon

Revision history for this message
Robie Basak (racb) wrote :

Tianon thinks it's reasonable? Status -> Triaged :-)

Changed in docker.io (Ubuntu):
status: New → Triaged
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.