GNU bug report logs - #76950
tramp caches non-existing podman containers

Previous Next

Full log

View this message in rfc822 format

From: Michael Albinus <michael.albinus <at> gmx.de>
To: Konstantin Kharlamov <Hi-Angel <at> yandex.ru>
Cc: 76950 <at> debbugs.gnu.org
Subject: bug#76950: tramp caches non-existing podman containers
Date: Wed, 12 Mar 2025 13:42:50 +0100

[Message part 1 (text/plain, inline)]

Konstantin Kharlamov <Hi-Angel <at> yandex.ru> writes:

Hi Konstantin,

> Figured, I'd clarify for people who don't work with containerization:
> the docker and podman completion is about auto-generated names like
> vibrant_hopper, frosty_northcutt, etc. Caching them has no use
> whatsoever, because:

That's not always the case. You can run a container with the
'--name="NAME"' argument.

> 1. The command that receives possible completions always fetches the
> current list, so even if cached containers still exist, the cache only
> wastes space.

Right. It doesn't make sense to offer container names which do not run,
but are cached.

> 2. When containers quit, the names become useless (the bug).

Not always (see above).

> So cache should not be working at all for both Podman and Docker.

Well, I've assembled a patch with disables completion of cached container
names for the docker, dockercp, podman and podmancp methods. See
appended. Could you, pls test?

It can be extended for other methods easily, which are offered by
tramp-container.el.

Best regards, Michael.

[Message part 2 (text/x-patch, attachment)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.