You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In my tests I sometimes have trouble restoring a container because the pid is already taken. I'm not sure why this is happening since it looks like FF already tries to jump ahead a bit in the PID space. Is there an easy way to avoid this?
[ff.run] (0.001s) Time is Sun, 06 Dec 2020 20:17:34 +0000
[ff.run] (0.001s) Host is da1273b3d3ec
[ff.run] (0.001s) Invocation ID is QIQ8Ea
[ff.run] (0.012s) Fetching image manifest for file:/tmp/ff-test
[ff.run] (0.014s) Restoring application
[ff.run] (0.499s) Uncompressed image size is 531 MiB, rate: 1099 MiB/s
set_ns_last_pid: WARN: Desired next pid 1001 is already taken
set_ns_last_pid: WARN: Desired next pid 1001 is already taken
set_ns_last_pid: WARN: Desired next pid 1001 is already taken
set_ns_last_pid: WARN: Desired next pid 1001 is already taken
set_ns_last_pid: WARN: Desired next pid 1001 is already taken
set_ns_last_pid: WARN: Desired next pid 1001 is already taken
pie: 1000: Error (criu/pie/restorer.c:1984): Unable to create a thread: 1002
pie: 1002: Error (criu/pie/restorer.c:615): Thread pid mismatch 1002/1001
pie: 1000: Error (criu/pie/restorer.c:2127): Restorer fail 1000
Error (criu/cr-restore.c:2583): Restoring FAILED.
In my tests I sometimes have trouble restoring a container because the pid is already taken. I'm not sure why this is happening since it looks like FF already tries to jump ahead a bit in the PID space. Is there an easy way to avoid this?
I'm using commands from the README:
(httpserv is just a simple go web server for testing; I'm using ubuntu 20.04 and FastFreeze 1.0.0)
The text was updated successfully, but these errors were encountered: