All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11076] New: Docker containerd installed to incorrect path
Date: Thu, 07 Jun 2018 07:05:54 +0000	[thread overview]
Message-ID: <bug-11076-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=11076

            Bug ID: 11076
           Summary: Docker containerd installed to incorrect path
           Product: buildroot
           Version: 2018.05
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned at buildroot.uclibc.org
          Reporter: sam at gpsm.co.uk
                CC: buildroot at uclibc.org
  Target Milestone: ---

In 2dccb4f2fefd8a0dbda65dd0f7537f811e920b13, the following change was made:

-define DOCKER_CONTAINERD_INSTALL_TARGET_CMDS
+define DOCKER_CONTAINERD_INSTALL_SYMLINKS
        ln -fs runc $(TARGET_DIR)/usr/bin/docker-runc
-       $(INSTALL) -D -m 0755 $(@D)/bin/containerd
$(TARGET_DIR)/usr/bin/docker-containerd
-       $(INSTALL) -D -m 0755 $(@D)/bin/containerd-shim
$(TARGET_DIR)/usr/bin/containerd-shim
        ln -fs containerd-shim $(TARGET_DIR)/usr/bin/docker-containerd-shim
 endef

This removed "/usr/bin/docker-containerd" without replacing it with a symlink

When I figure out how I will create a patch and send to the mailer

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2018-06-07  7:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-07  7:05 bugzilla at busybox.net [this message]
2018-06-07 14:05 ` [Buildroot] [Bug 11076] Docker containerd installed to incorrect path bugzilla at busybox.net

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=bug-11076-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.