Github messages for voidlinux
 help / color / mirror / Atom feed
From: endigma <endigma@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: docker: "docker-init": executable file not found in $PATH
Date: Tue, 20 Apr 2021 05:41:23 +0200	[thread overview]
Message-ID: <20210420034123.hkvRLYzO8CwutHmBz3YwRN2KDwQSVk9RBkO1wXuZoK0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30341@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 896 bytes --]

New comment by endigma on void-packages repository

https://github.com/void-linux/void-packages/issues/30341#issuecomment-822948252

Comment:
I don't have this issue, could you send more details about your error case? docker-init isn't a command provided by docker-cli. If you need this binary, I suggest implementing it as a separate package. We don't pull in tini-static or tini at all because this isn't really necessary for most people.

Alternatively, if you believe this is functionality that should be provided by default, PR in the fix, should just be a symlink and a depend. I believe the best approach here would be to provide a separate package that does this, as I don't need tini-static nor do many other docker users.

If you do decide that making it included is the best approach, ensure the tini binary is statically linked, as this binary is run INSIDE the docker container.

  parent reply	other threads:[~2021-04-20  3:41 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-20  1:56 [ISSUE] " pudiva
2021-04-20  2:20 ` pudiva
2021-04-20  2:27 ` endigma
2021-04-20  2:27 ` endigma
2021-04-20  2:28 ` endigma
2021-04-20  3:01 ` pudiva
2021-04-20  3:02 ` pudiva
2021-04-20  3:10 ` pudiva
2021-04-20  3:11 ` ericonr
2021-04-20  3:11 ` ericonr
2021-04-20  3:34 ` endigma
2021-04-20  3:38 ` endigma
2021-04-20  3:39 ` endigma
2021-04-20  3:41 ` endigma [this message]
2021-04-20  5:19 ` thypon
2021-04-20  5:41 ` endigma
2021-04-20  5:41 ` endigma
2021-04-20  5:42 ` endigma
2021-04-20  5:45 ` thypon
2021-04-20  5:47 ` endigma
2021-04-20  5:49 ` ericonr
2021-04-20  5:53 ` thypon
2021-04-20  5:54 ` endigma
2021-04-20  5:54 ` endigma
2021-04-20  5:56 ` endigma
2021-04-20  5:57 ` thypon
2021-04-20  5:58 ` endigma
2021-04-20  6:03 ` thypon
2021-04-20  6:03 ` thypon
2021-04-20  6:04 ` thypon
2021-04-20  6:05 ` thypon
2021-04-20 10:30 ` ahesford
2021-04-20 10:45 ` ahesford
2021-04-20 13:19 ` pudiva
2021-04-20 13:44 ` ericonr
2021-04-20 13:44 ` ericonr
2021-04-20 13:44 ` ericonr
2021-04-20 14:14 ` sgn
2021-04-20 14:33 ` endigma
2021-04-20 14:33 ` endigma
2021-04-20 14:37 ` thypon
2021-04-20 14:37 ` thypon
2021-04-20 14:42 ` thypon
2021-04-20 14:45 ` endigma
2021-04-20 15:24 ` ahesford
2021-04-20 15:42 ` endigma
2021-04-20 15:44 ` endigma
2021-04-20 15:47 ` pudiva
2021-04-20 16:17 ` endigma
2021-05-03 18:32 ` Skaytacium
2021-05-03 18:36 ` endigma
2021-05-03 18:36 ` endigma
2021-05-03 18:39 ` Skaytacium
2021-05-04 10:38 ` pudiva
2021-05-04 10:38 ` [ISSUE] [CLOSED] " pudiva
2023-06-25 17:19 ` hholst80
2023-06-25 17:22 ` hholst80
2023-06-25 17:32 ` classabbyamp
2023-06-25 18:52 ` endigma
2023-06-25 18:52 ` endigma

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210420034123.hkvRLYzO8CwutHmBz3YwRN2KDwQSVk9RBkO1wXuZoK0@z \
    --to=endigma@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /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.
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 NNTP newsgroup(s).