cri-o/lib
Antonio Murdaca a0157078ad
sandbox: fix sandbox logPath when crio restarts
We weren't setting the logPath of the sandbox when restoring sandboxes
and containers upon a crio restarts. That means that if you restart
CRI-O you get sandboxes with empty logPath. That means that when you're
starting a container in a restored sandbox you get a relative logPath
for the container:

sandboxLogPath: "/var/something"
- restore
sandboxLogPath: ""
- create container foo
containerLogPath: "foo_attempt.log"

With this patch we actually get an absolute path (which is correct):

sandboxLogPath: "/var/something"
- restore
sandboxLogPath: "/var/something"
- create container foo
containerLogPath: "/var/something/foo_attempt.log"

Signed-off-by: Antonio Murdaca <runcom@redhat.com>
2018-02-09 15:54:47 +01:00
..
sandbox lib,oci: drop stateLock when possible 2017-12-15 15:31:58 +01:00
testdata libkpod -> lib rename 2017-11-30 17:08:26 +01:00
config.go libkpod -> lib rename 2017-11-30 17:08:26 +01:00
config_test.go libkpod -> lib rename 2017-11-30 17:08:26 +01:00
container.go libkpod -> lib rename 2017-11-30 17:08:26 +01:00
container_server.go sandbox: fix sandbox logPath when crio restarts 2018-02-09 15:54:47 +01:00
hooks.go Merge pull request #1235 from rhatdan/hooks 2018-02-03 09:51:59 -08:00
kill.go libkpod -> lib rename 2017-11-30 17:08:26 +01:00
logs.go libkpod -> lib rename 2017-11-30 17:08:26 +01:00
pause.go libkpod -> lib rename 2017-11-30 17:08:26 +01:00
remove.go libkpod -> lib rename 2017-11-30 17:08:26 +01:00
rename.go libkpod -> lib rename 2017-11-30 17:08:26 +01:00
stats.go libkpod -> lib rename 2017-11-30 17:08:26 +01:00
stop.go libkpod -> lib rename 2017-11-30 17:08:26 +01:00
wait.go libkpod -> lib rename 2017-11-30 17:08:26 +01:00