unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Brian Cully via "Emacs development discussions." <emacs-devel@gnu.org>
To: Michael Albinus <Michael.Albinus@gmx.de>
Cc: miha@kamnitnik.top, Brian Cully <bjc@kublai.com>, emacs-devel@gnu.org
Subject: Re: master 152c7322c1: * lisp/net/tramp-docker.el: New file.
Date: Tue, 4 Oct 2022 14:17:00 -0400	[thread overview]
Message-ID: <14f86fb6-0191-0a04-b8f1-88dceaa00dc4@spork.org> (raw)
In-Reply-To: <874jwjmptk.fsf@gmx.de>

On 10/4/22 14:00, Michael Albinus wrote:
> Brian Cully <bjc@spork.org> writes:
> 
> Hi Brian,
> 
>> This is just a copy of the Docker docs, but s/docker/podman/. I'm not
>> really all that familiar with texinfo, so I hope this is okay.
> 
> I like to phrase the description for every method a little bit
> different. What about
> 
> --8<---------------cut here---------------start------------->8---
> Podman is a drop-in replacement for docker.  It runs rootless.  A
> container is accessed via
> @file{@trampfn{podman,user@@container,/path/to/file}}, where
> @samp{user} is the (optional) user that you want to use, and
> @samp{container} is the name or id of the container.
> --8<---------------cut here---------------end--------------->8---
> 
>> -bjc
> 
> Best regards, Michael.

Podman is not always run rootless (I cannot, for instance, because my 
file system doesn't support openat2(2), which podman requires for 
rootless containers).

What about:

-[snip]-
Podman is a docker alternative which may be run rootless, if desired. 
Files are accessed via …
-[snip]-

It also looks like only the "docker" and "tramp" methods have examples 
given of their file names. Should those parts be removed?

-bjc



  reply	other threads:[~2022-10-04 18:17 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
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. [this message]
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=14f86fb6-0191-0a04-b8f1-88dceaa00dc4@spork.org \
    --to=emacs-devel@gnu.org \
    --cc=Michael.Albinus@gmx.de \
    --cc=bjc@kublai.com \
    --cc=bjc@spork.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).