From: Michael Albinus <Michael.Albinus@gmx.de>
To: miha@kamnitnik.top
Cc: Brian Cully <bjc@kublai.com>, emacs-devel@gnu.org
Subject: Re: master 152c7322c1: * lisp/net/tramp-docker.el: New file.
Date: Thu, 29 Sep 2022 19:28:08 +0200 [thread overview]
Message-ID: <87zgeihyzb.fsf@gmx.de> (raw)
In-Reply-To: <875yh6untf.fsf@miha-pc> (miha@kamnitnik.top's message of "Thu, 29 Sep 2022 18:50:52 +0200")
miha@kamnitnik.top writes:
Hi Miha,
>> +(defcustom tramp-docker-program "docker"
>> + "Name of the Docker client program."
>> + :type '(choice (const "docker")
>> + (const "podman")
>> + (string))
>> + :group 'tramp-docker)
>
> It's not unusual to have both podman and docker containers on the same
> host. But the way tramp-docker.el is arranged currently, it's difficult
> to have simultaneous tramp connections to both of them. I think it would
> make sense to have two tramp methods: '/docker:' and '/podman:', and by
> extension, two defcustoms: tramp-docker-program and
> tramp-podman-program.
I agree. Especially, when we have multi-hops to different machines,
which could offer either docker or podman executables.
Brian?
Best regards, Michael.
next prev parent reply other threads:[~2022-09-29 17:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-29 16:50 master 152c7322c1: * lisp/net/tramp-docker.el: New file miha
2022-09-29 17:28 ` Michael Albinus [this message]
2022-10-03 13:44 ` Brian Cully via Emacs development discussions.
2022-10-03 17:37 ` Michael Albinus
2022-10-04 15:32 ` Brian Cully via Emacs development discussions.
2022-10-04 16:58 ` Michael Albinus
2022-10-04 17:43 ` Brian Cully via Emacs development discussions.
2022-10-04 18:00 ` Michael Albinus
2022-10-04 18:17 ` Brian Cully via Emacs development discussions.
2022-10-04 18:20 ` Michael Albinus
2022-10-04 18:33 ` Brian Cully via Emacs development discussions.
2022-10-04 18:36 ` Michael Albinus
2022-10-04 18:45 ` Brian Cully via Emacs development discussions.
2022-10-04 19:21 ` Michael Albinus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zgeihyzb.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=bjc@kublai.com \
--cc=emacs-devel@gnu.org \
--cc=miha@kamnitnik.top \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).