Skip to content

Conversation

@baude
Copy link
Member

@baude baude commented Nov 8, 2017

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

@mheon
Copy link
Member

mheon commented Nov 8, 2017

LGTM pending tests. @rhatdan PTAL

@rhatdan
Copy link
Member

rhatdan commented Nov 8, 2017

@alexlarsson PTAL

Copy link
Member

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
Copy link
Member

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?

Copy link
Member

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

Copy link
Member Author

Choose a reason for hiding this comment

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

fixed

@baude baude force-pushed the attach branch 2 times, most recently from 6447483 to f8312ed Compare November 9, 2017 00:21
cmd/kpod/run.go Outdated
Copy link
Member

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?

@alexlarsson
Copy link
Contributor

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?

@baude
Copy link
Member Author

baude commented Nov 9, 2017

@alexlarsson we dont use conmon to attach. We attach to the socket which is already created.

@baude
Copy link
Member Author

baude commented Nov 9, 2017

bot, retest this please

@rhatdan
Copy link
Member

rhatdan commented Nov 9, 2017

@rh-atomic-bot r+

@rh-atomic-bot
Copy link
Collaborator

📌 Commit f8312ed has been approved by rhatdan

@rh-atomic-bot
Copy link
Collaborator

⌛ Testing commit f8312ed with merge 8cad4d9...

rh-atomic-bot pushed a commit that referenced this pull request Nov 9, 2017
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
@baude
Copy link
Member Author

baude commented Nov 9, 2017

bot, retest this please

@baude baude force-pushed the attach branch 2 times, most recently from ea2e58b to feb5aa4 Compare November 9, 2017 17:14
@mheon
Copy link
Member

mheon commented Nov 9, 2017

LGTM. Let's give this another show
@rh-atomic-bot r+

@rh-atomic-bot
Copy link
Collaborator

📌 Commit feb5aa4 has been approved by mheon

@rh-atomic-bot
Copy link
Collaborator

⌛ Testing commit feb5aa4 with merge f50f308...

@baude
Copy link
Member Author

baude commented Nov 9, 2017

@rh-atomic-bot retry

@rh-atomic-bot
Copy link
Collaborator

⌛ Testing commit feb5aa4 with merge 4afb998...

@rh-atomic-bot
Copy link
Collaborator

💥 Test timed out

@rhatdan
Copy link
Member

rhatdan commented Nov 10, 2017

@rh-atomic-bot retry

@rh-atomic-bot
Copy link
Collaborator

⌛ Testing commit feb5aa4 with merge 35ab89e...

rh-atomic-bot pushed a commit that referenced this pull request Nov 10, 2017
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
@rhatdan
Copy link
Member

rhatdan commented Nov 10, 2017

@baude The tests are still not completing?

@rh-atomic-bot
Copy link
Collaborator

💥 Test timed out

@rhatdan
Copy link
Member

rhatdan commented Nov 13, 2017

This patch passed when I combined it with mine. I don't know why it is timing out here.
#21

@baude
Copy link
Member Author

baude commented Nov 14, 2017

@rh-atomic-bot retry

@rh-atomic-bot
Copy link
Collaborator

⌛ Testing commit feb5aa4 with merge fbdb70c...

@rh-atomic-bot
Copy link
Collaborator

💥 Test timed out

.papr.yml Outdated
Copy link
Contributor

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.

@baude baude force-pushed the attach branch 3 times, most recently from a26ae16 to 956a4ff Compare November 14, 2017 16:57
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>
@baude
Copy link
Member Author

baude commented Nov 14, 2017

@rh-atomic-bot bot, retest this please

@baude
Copy link
Member Author

baude commented Nov 14, 2017

bot, retest this please

@baude baude closed this Nov 15, 2017
@baude baude deleted the attach branch December 22, 2019 18:44
@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 26, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 26, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants