This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1857257

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

** Changed in: linux (Ubuntu)
       Status: New => Incomplete

** Tags added: disco

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1857257

Title:
  linux-image-5.0.0-35-generic breaks checkpointing of container

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Trying to checkpoint a container (docker/podman) on 18.04 fails
  starting with linux-image-5.0.0-35-generic. We (CRIU upstream) see
  this in Travis starting a few weeks ago. Manually testing it locally
  shows that linux-image-5.0.0-32-generic still works and linux-
  image-5.0.0-35-generic does not longer work. It seems to be overlayfs
  related, at least that is what we believe. The CRIU error message we
  see is:

  (00.170944) Error (criu/files-reg.c:1277): Can't lookup mount=410 for fd=-3 
path=/bin/busybox
  (00.170987) Error (criu/cr-dump.c:1246): Collect mappings (pid: 1637) failed 
with -1

  
  We have not seen this only in Travis, but also multiple CRIU users reported 
that bug already. Currently we have to tell them to downgrade the kernel.

  I also able to reproduce it with linux-image-5.3.0-24-generic. Staying
  on the 4.18.0 kernel series does not show this error.
  4.18.0-25-generic works without problems.

  See also https://github.com/checkpoint-restore/criu/issues/860

  One of the possible explanations from our side include:

  "Looks like we have the same as for st_dev now with mnt_id, that is
  bad, because we can't find on which mount to open the file if kernel
  hides these information from us."

  Running on the upstream 5.5.0-rc1 kernel does not show this error.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857257/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to