podman/podman-rename.1.md at 95c4637851fed03e1579a8bb4a53204a7f43582c

mirror of https://github.com/containers/podman.git synced 2025-05-24 18:46:26 +08:00

Files

Matthew Heon 997de2f8e9 Initial implementation of renaming containers

Basic theory: We remove the container, but *only from the DB*.
We leave it in c/storage, we leave the lock allocated, we leave
it running (if it is). Then we create an identical container with
an altered name, and add that back to the database. Theoretically
we now have a renamed container.

The advantage of this approach is that it doesn't just apply to
rename - we can use this to make *any* configuration change to a
container that does not alter its container ID.

Potential problems are numerous. This process is *THOROUGHLY*
non-atomic at present - if you `kill -9` Podman mid-rename things
will be in a bad place, for example. Also, we can't rename
containers that can't be removed normally - IE, containers with
dependencies (pod infra containers, for example).

The largest potential improvement will be to move the majority of
the work into the DB, with a `RecreateContainer()` method - that
will add atomicity, and let us remove the container without
worrying about depencies and similar issues.

Potential problems: long-running processes that edit the DB and
may have an older version of the configuration around. Most
notable example is `podman run --rm` - the removal command needed
to be manually edited to avoid this one. This begins to get at
the heart of me not wanting to do this in the first place...

This provides CLI and API implementations for frontend, but no
tunnel implementation. It will be added in a future release (just
held back for time now - we need this in 3.0 and are running low
on time).

This is honestly kind of horrifying, but I think it will work.

Signed-off-by: Matthew Heon <mheon@redhat.com>

2021-01-14 18:29:28 -05:00

925 B

Raw Blame History

% podman-rename(1)

NAME

podman-rename - Rename an existing container

SYNOPSIS

podman rename container newname

podman container rename container newname

DESCRIPTION

Rename changes the name of an existing container. The old name will be freed, and will be available for use. This command can be run on containers in any state. However, running containers may not fully receive the effects until they are restarted - for example, a running container may still use the old name in its logs. At present, only containers are supported; pods and volumes cannot be renamed.

OPTIONS

EXAMPLES

# Rename a container by name
$ podman rename oldContainer aNewName

# Rename a container by ID
$ podman rename 717716c00a6b testcontainer

# Use the container rename alias
$ podman container rename 6e7514b47180 databaseCtr

925 B Raw Blame History