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.

Sign up for GitHub

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

README: update "out of scope" section #2428

Merged
merged 1 commit into from
Feb 26, 2019
Merged

README: update "out of scope" section #2428

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 9 additions & 4 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,10 +31,15 @@ This project tests all builds against each supported version of Fedora, the late

## Out of scope

* Signing and pushing images to various image storages.
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 leave this, with a note that Podman does it, but we still recommend Skopeo for serious work? Our sign/verify code isn't as mature as theirs

See [Skopeo](https://github.com/containers/skopeo/).
* Container Runtimes daemons for working with the Kubernetes CRI interface.
See [CRI-O](https://github.com/kubernetes-sigs/cri-o).
* Specializing in signing and pushing images to various storage backends.
Copy link
Member

Choose a reason for hiding this comment

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

I like how you handled this @vrothberg

See [Skopeo](https://github.com/containers/skopeo/) for those tasks.
* Container runtimes daemons for working with the Kubernetes CRI interface.
[CRI-O](https://github.com/kubernetes-sigs/cri-o) specializes in that.
* Supporting `docker-compose`. We believe that Kubernetes is the defacto
standard for container orchestration. Hence, Podman allows the creation of
Pods from a Kubernetes YAML file. See
Copy link

Choose a reason for hiding this comment

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

This doesn't make sense as a term for out of scope. docker-compose is not the same as Docker Swarm. Essentially, docker-compose is a way to spin up a pod on your machine using your single container engine instance.

Making someone deploy Kubernetes for that is madness. However, it is nice that podman can generate Kubernetes YAML for translation to a Kubernetes system, it makes no sense to not have the facility built in so that people can develop these things to eventually host in an OpenShift/Kubernetes system.

Copy link
Member

Choose a reason for hiding this comment

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

docker compose is not part of Docker it is a separate project. And it is Huge. So we currently do not have the man power to do everything that is involved in doing this. If someone wants to start a project called podman-compose, then we would support them.

We don't want to force anyone to do kubernetes. We are just suggesting alternatives and looking at the problem from a different point of view.

Copy link
Member Author

Choose a reason for hiding this comment

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

This doesn't make sense as a term for out of scope. docker-compose is not the same as Docker Swarm. Essentially, docker-compose is a way to spin up a pod on your machine using your single container engine instance.

Right. You can use podman play kube in a similar fashion but with Kubernetes yaml.

Making someone deploy Kubernetes for that is madness. However, it is nice that podman can generate Kubernetes YAML for translation to a Kubernetes system, it makes no sense to not have the facility built in so that people can develop these things to eventually host in an OpenShift/Kubernetes system.

I suggest cooling down a bit.

Noone is forcing users into Kubernetes. podman play kube is meant for the exact use-case you describe but it requires a Kubernetes yaml instead of Compose yaml.

You were referring to podman generate kube which generates this yaml file based on a set of containers/pods and allows migrating to Kubernetes, if desired.

However, the text must be corrected as it was meant to refer to podman-play-kube.

Copy link
Member Author

Choose a reason for hiding this comment

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

However, the text must be corrected as it was meant to refer to podman-play-kube.

Actually, it's fine in this regard: "Hence, Podman allows the creation of Pods from a Kubernetes YAML file."

Not sure if we should avoid mentioning "orchestrating" and rephrase it.

[podman-play-kube](https://github.com/containers/libpod/blob/master/docs/podman-play-kube.1.md)
Copy link
Member

Choose a reason for hiding this comment

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

Link generate too

Copy link
Member

Choose a reason for hiding this comment

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

Are you going to add generate too per @mheon's suggestion?

Copy link
Member Author

Choose a reason for hiding this comment

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

Sorry, the PR is in already. Shall I update? I think that the podman play manpage could mention it as well.

Copy link
Member

Choose a reason for hiding this comment

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

Sure open a new PR.

for more details.

## OCI Projects Plans

Expand Down