Skip to content

--init-path does not seem to work. #32355

@andyneff

Description

@andyneff

While using --init works and execute tini 0.13.0. However, I cannot figure out how to use --init-path to change the init binary used.

Steps to reproduce the issue:

  1. docker run -it --rm --init --init-path=/usr/local/bin/tini --entrypoint=bash krallin/ubuntu-tini
  2. /proc/1/exe -h

Describe the results you received:

exe (tini version 0.13.0 - git.949e6fa)

Describe the results you expected:

tini (tini version 0.13.2 - git.79016ec)

Additional information you deem important (e.g. issue happens only occasionally):

I also tries pointing --init-path to a path on the host as suggested on krallin/tini#81, and that did not help either.

Output of docker version:

Client:
 Version:      17.03.0-ce
 API version:  1.26
 Go version:   go1.7.5
 Git commit:   60ccb22
 Built:        Thu Feb 23 11:02:43 2017
 OS/Arch:      linux/amd64

Server:
 Version:      17.03.0-ce
 API version:  1.26 (minimum version 1.12)
 Go version:   go1.7.5
 Git commit:   60ccb22
 Built:        Thu Feb 23 11:02:43 2017
 OS/Arch:      linux/amd64
 Experimental: false

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/cliClientarea/daemonCore Enginekind/bugBugs are bugs. The cause may or may not be known at triage time so debugging may be needed.version/17.03

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions