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

Rich container implementation #25

Closed
allencloud opened this issue Oct 30, 2017 · 1 comment · Fixed by #767
Closed

Rich container implementation #25

allencloud opened this issue Oct 30, 2017 · 1 comment · Fixed by #767
Assignees
Labels
kind/feature kind/feature-request This is a feature request from community for PouchContainer

Comments

@allencloud
Copy link
Collaborator

Issue Description
Rich container is a very valuable feature of container technology. With the popular docker's concept, we should always run a single process or application in one single container. It seems to simplify process management in container. However it would affect application itself. This would be somewhat invasive to application which is definitely not a good way.

While rich container is one kind of container which could bear other system service running in container to help application run with whatever it wants. More specifically, we construct a system init process in the initialization of container.

Describe what happened:
Currently one single process or application in the only way suggested.

Describe what you expected to happen:
Rich container can be implemented in Pouch.

@allencloud allencloud added kind/feature kind/feature-request This is a feature request from community for PouchContainer labels Oct 30, 2017
@allencloud
Copy link
Collaborator Author

I think this has been implemented in PR #767. Closing this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature kind/feature-request This is a feature request from community for PouchContainer
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants