From: hholst80 <hholst80@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: docker: "docker-init": executable file not found in $PATH
Date: Sun, 25 Jun 2023 19:22:30 +0200 [thread overview]
Message-ID: <20230625172230.a5C37rcmoES4CzpIzqrHbFZ1SvxKTthj2s1NFb4QtTU@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: 831 bytes --]
New comment by hholst80 on void-packages repository
https://github.com/void-linux/void-packages/issues/30341#issuecomment-1606171026
Comment:
Please re-open this. I cannot understand how this could be allowed to pass through. docker-init must be shipped with the core docker package. If that is via direct shipping it or a required dependency is immaterial but it must work out of the box to pass --init to docker run otherwise the installation is broken.
There is no formal dependency between tini and docker. Docker might use tini to implement it's init service, but the relationship is now the opposite. There should be a symlink in docker to tini-static and docker should have tini as a dependency.
[I] root@trump ~# xlocate docker-init
tini-0.19.0_2 /usr/bin/docker-init -> /usr/bin/tini-static
Ping @pudiva
next prev parent reply other threads:[~2023-06-25 17:22 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
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 [this message]
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=20230625172230.a5C37rcmoES4CzpIzqrHbFZ1SvxKTthj2s1NFb4QtTU@z \
--to=hholst80@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).