aboutsummaryrefslogtreecommitdiff
path: root/libpod/boltdb_state_internal.go
diff options
context:
space:
mode:
authorMatthew Heon <matthew.heon@pm.me>2020-07-28 15:59:58 -0400
committerMatthew Heon <mheon@redhat.com>2020-10-20 09:20:33 -0400
commitf9655d92d660bad46a992831605960767fedc44a (patch)
tree5656073b4cd775ae00e9c01e0ac3757ab5d9e23a /libpod/boltdb_state_internal.go
parent35b4cb196545eee3b072083e716ad4588e0bb486 (diff)
downloadpodman-f9655d92d660bad46a992831605960767fedc44a.tar.gz
podman-f9655d92d660bad46a992831605960767fedc44a.tar.bz2
podman-f9655d92d660bad46a992831605960767fedc44a.zip
When given OCI runtime by path, use path as name
Say I start a container with the flag `--runtime /usr/local/sbin/crun`. I then stop the container, and restart it without the flag. We previously stored the runtime in use by a container only by basename when given a path, so the container only knows that it's using the `crun` OCI runtime - and on being restarted without the flag, it will use the system crun, not my special crun build. Using the full path as the name in these cases ensures we will still use the correct runtime, even on subsequent runs of Podman. Signed-off-by: Matthew Heon <matthew.heon@pm.me>
Diffstat (limited to 'libpod/boltdb_state_internal.go')
0 files changed, 0 insertions, 0 deletions