Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

remove --init-path from client #32470

Merged
merged 1 commit into from
Apr 25, 2017
Merged

Conversation

runcom
Copy link
Member

@runcom runcom commented Apr 10, 2017

Fix #32355

@justincormack @thaJeztah PTAL

Signed-off-by: Antonio Murdaca runcom@redhat.com

@thaJeztah
Copy link
Member

Oh, I think we should keep the --init, just remove the --init-path. Allowing users to enable/disable --init per container is fine, but specifying a different path per container didn't work, and didn't make much sense, as the --init-path was added to allow the init binary to be in a custom location on some distros

@justincormack
Copy link
Contributor

Yes, the boolean should still be there to enable/disable on a per run basis....

@runcom
Copy link
Member Author

runcom commented Apr 10, 2017

updated to leave --init

@runcom runcom changed the title remove --init[-path] from client remove --init-path from client Apr 10, 2017
Copy link
Member

@vdemeester vdemeester left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 🐻

@thaJeztah
Copy link
Member

ugh, needs a rebase @runcom 😢

Signed-off-by: Antonio Murdaca <runcom@redhat.com>
@runcom
Copy link
Member Author

runcom commented Apr 10, 2017

rebased!

@vieux
Copy link
Contributor

vieux commented Apr 10, 2017

@thaJeztah shouldn't we deprecate instead of removing ?

@thaJeztah
Copy link
Member

thaJeztah commented Apr 10, 2017

@vieux we could keep the flag; point is that the flag never was intended to be on docker run / docker create, and it even looks like it never worked;

docker run --init-path=/hello/world --init -dit --name foobar busybox

docker inspect foobar | grep world
<empty>
/ # docker top foobar
PID                 USER                TIME                COMMAND
227                 root                0:00                /dev/init -- sh
252                 root                0:00                sh

@thaJeztah thaJeztah added this to the 17.05.0 milestone Apr 10, 2017
@runcom
Copy link
Member Author

runcom commented Apr 18, 2017

ping @thaJeztah where are we on this?

@runcom
Copy link
Member Author

runcom commented Apr 24, 2017

Anyone? 👼

Copy link
Contributor

@mlaventure mlaventure left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Given that it doesn't look that it was saved on disk, I'm fine with removing it outright.

thaJeztah added a commit to thaJeztah/docker-py that referenced this pull request Apr 10, 2019
This option was never functional, and was not intended
to be added to the "container create" API, so let's
remove it, because it has been removed in Docker 17.05,
and was broken in versions before that; see

- moby/moby#32355 --init-path does not seem to work
- moby/moby#32470 remove --init-path from client

Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
thaJeztah added a commit to thaJeztah/docker.github.io that referenced this pull request Apr 11, 2019
This option was never functional, and was not intended
to be added to the "container create" API, so let's
remove it, because it has been removed in Docker 17.05,
and was broken in versions before that; see

- docker/docker-py#2309 Remove init_path from create
- moby/moby#32355 --init-path does not seem to work
- moby/moby#32470 remove --init-path from client

Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
thaJeztah added a commit to thaJeztah/docker.github.io that referenced this pull request Apr 11, 2019
This option was never functional, and was not intended
to be added to the "container create" API, so let's
remove it, because it has been removed in Docker 17.05,
and was broken in versions before that; see

- docker/docker-py#2309 Remove init_path from create
- moby/moby#32355 --init-path does not seem to work
- moby/moby#32470 remove --init-path from client

Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
bermudezmt pushed a commit to docker/docs that referenced this pull request Apr 12, 2019
* compose-file: remove reference to custom init path

This option was never functional, and was not intended
to be added to the "container create" API, so let's
remove it, because it has been removed in Docker 17.05,
and was broken in versions before that; see

- docker/docker-py#2309 Remove init_path from create
- moby/moby#32355 --init-path does not seem to work
- moby/moby#32470 remove --init-path from client

Signed-off-by: Sebastiaan van Stijn <github@gone.nl>

* Update index.md
tcaiazzi pushed a commit to tcaiazzi/docker-py that referenced this pull request Mar 4, 2020
This option was never functional, and was not intended
to be added to the "container create" API, so let's
remove it, because it has been removed in Docker 17.05,
and was broken in versions before that; see

- moby/moby#32355 --init-path does not seem to work
- moby/moby#32470 remove --init-path from client

Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants