-
Notifications
You must be signed in to change notification settings - Fork 2.9k
Fix terminal attach #32
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
Conversation
|
LGTM pending tests. @rhatdan PTAL |
|
@alexlarsson PTAL |
cmd/kpod/create.go
Outdated
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.
What happens if you set detach and tty?
cmd/kpod/run.go
Outdated
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.
Shouldn't this happen if you specify -d?
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.
Yes, this should still happen
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.
fixed
6447483 to
f8312ed
Compare
cmd/kpod/run.go
Outdated
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.
Should we be waiting down here or up higher before the start?
|
How can we attach to the container before it is started? There is no conmon to attach to by then. I must be missing something here? |
|
@alexlarsson we dont use conmon to attach. We attach to the socket which is already created. |
|
bot, retest this please |
|
📌 Commit f8312ed has been approved by |
|
⌛ Testing commit f8312ed with merge 8cad4d9... |
Re-order the startup of a new container via run from initialize > start > attach to initialize > attach > start. This fixes output when running: kpod run -i -t IMAGE command and kpod run IMAGE command Signed-off-by: baude <bbaude@redhat.com> Closes: #32 Approved by: rhatdan
|
bot, retest this please |
ea2e58b to
feb5aa4
Compare
|
LGTM. Let's give this another show |
|
📌 Commit feb5aa4 has been approved by |
|
⌛ Testing commit feb5aa4 with merge f50f308... |
|
@rh-atomic-bot retry |
|
⌛ Testing commit feb5aa4 with merge 4afb998... |
|
💥 Test timed out |
|
@rh-atomic-bot retry |
|
⌛ Testing commit feb5aa4 with merge 35ab89e... |
Re-order the startup of a new container via run from initialize > start > attach to initialize > attach > start. This fixes output when running: kpod run -i -t IMAGE command and kpod run IMAGE command Signed-off-by: baude <bbaude@redhat.com> Closes: #32 Approved by: mheon
|
@baude The tests are still not completing? |
|
💥 Test timed out |
|
This patch passed when I combined it with mine. I don't know why it is timing out here. |
|
@rh-atomic-bot retry |
|
⌛ Testing commit feb5aa4 with merge fbdb70c... |
|
💥 Test timed out |
.papr.yml
Outdated
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.
This is throwing off the parser (need to strengthen that...). It's expecting a number followed by one of s, m, or h. See https://github.com/projectatomic/papr/blob/master/docs/sample.papr.yml#L172.
a26ae16 to
956a4ff
Compare
Re-order the startup of a new container via run from initialize > start > attach to initialize > attach > start. This fixes output when running: kpod run -i -t IMAGE command and kpod run IMAGE command Signed-off-by: baude <bbaude@redhat.com>
|
@rh-atomic-bot bot, retest this please |
|
bot, retest this please |
Re-order the startup of a new container via run from
initialize > start > attach to initialize > attach > start.
This fixes output when running:
kpod run -i -t IMAGE command
and
kpod run IMAGE command
Signed-off-by: baude bbaude@redhat.com