-
Notifications
You must be signed in to change notification settings - Fork 18.6k
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
Conversation
Oh, I think we should keep the |
Yes, the boolean should still be there to enable/disable on a per run basis.... |
4741ff1
to
422b795
Compare
updated to leave |
422b795
to
89f3d00
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 🐻
ugh, needs a rebase @runcom 😢 |
Signed-off-by: Antonio Murdaca <runcom@redhat.com>
rebased! |
89f3d00
to
a18d103
Compare
@thaJeztah shouldn't we deprecate instead of removing ? |
@vieux we could keep the flag; point is that the flag never was intended to be on 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 |
ping @thaJeztah where are we on this? |
Anyone? 👼 |
There was a problem hiding this 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.
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>
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>
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>
* 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
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>
Fix #32355
@justincormack @thaJeztah PTAL
Signed-off-by: Antonio Murdaca runcom@redhat.com