-
Notifications
You must be signed in to change notification settings - Fork 39
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
Add podman as an option when using kind #415
Conversation
Welcome @giulianisanches! It looks like this is your first PR to knative-sandbox/kn-plugin-quickstart 🎉 |
Hi @giulianisanches. Thanks for your PR. I'm waiting for a knative-sandbox member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/ok-to-test |
I have opened this PR to get some feedback as I'm not a Go developer :). Feel free to ping me and ask for improvements and fixes :) Thank you very much. |
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.
Thanks for the PR! Left a few comments.
You'll also need to sign the CLA before this can be merged.
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.
Looks like podman is running into issues trying to expose port 80...
$ ./kn-quickstart kind
<snip>
ERROR: failed to create cluster: command "podman run --name knative-control-plane --hostname knative-control-plane --label io.x-k8s.kind.role=control-plane --privileged --tmpfs /tmp --tmpfs /run --volume 42da644ee9028ed18a6873b4dce9b6d690ef8284853806bce51b0e48c8533c9f:/var:suid,exec,dev --volume /lib/modules:/lib/modules:ro -e KIND_EXPERIMENTAL_CONTAINERD_SNAPSHOTTER --detach --tty --net kind --label io.x-k8s.kind.cluster=knative -e container=podman --device /dev/fuse --publish=127.0.0.1:80:31080/tcp --publish=127.0.0.1:43605:6443/tcp -e KUBECONFIG=/etc/kubernetes/admin.conf docker.io/kindest/node:v1.25.3" failed with error: exit status 126
Command Output: Error: rootlessport cannot expose privileged port 80, you can add 'net.ipv4.ip_unprivileged_port_start=80' to /etc/sysctl.conf (currently 1024), or choose a larger port number (>= 1024): listen tcp 127.0.0.1:80: bind: permission denied
Error: creating cluster: existing cluster: new cluster: kind create: piping output: exit status 1
<snip>
Changing the port (both here and in the kourier install) leads to another error, when trying to connect to the registry:
$ podman network connect kind kind-registry
Error: "slirp4netns" is not supported: invalid network mode
Hi, sorry for the lack of activity. I will get back on this next sunday afternoon. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: giulianisanches The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
This error message is related to when we fail to connect to local registry
It was not working because it try to combine both `&&` and `||`. The result command is `podman rm -f <...> && || true` When it should be podman `rm -f <...> && true` or `podman rm -f <...> || true`. Removing this combination allow the error to be handled when the deleteContainerRegistry is called.
This is fixed in the upstream, but my rebase didn't got this change.
This error message is related to when we fail to connect to local registry
It was not working because it try to combine both `&&` and `||`. The result command is `podman rm -f <...> && || true` When it should be podman `rm -f <...> && true` or `podman rm -f <...> || true`. Removing this combination allow the error to be handled when the deleteContainerRegistry is called.
Again, sorry for the lack of activity. I have reviewed all the comments and also tried to rebase my code with yours and I hope to have made everything right. |
Some of the diffs on your PR seem a bit out of whack... I don't think you should have any changes other than in |
ok, that's better 😄 |
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.
I'm still running into the issues from #415 (review)
We need to address the port issue (probably by not using port 80) and that podman network connect
is unimplemented for slirp4netns mode as per kubernetes-sigs/kind#2694 (comment)
I have merged the changes from upstream:main into my fork. Maybe these are the changes that you're menioning. |
Changing the port to 8080 and running the command './kn-quickstart kind' i get the following output:
The command
Operating system:
|
Additional references: |
I have the following containers running on my machine:
For the
For the
Trying to connect to the
I will try to create the EDITED: Turns out that when you run Time to get some sleep :) |
This Pull Request is stale because it has been open for 90 days with |
sorry about the lack of update, but I will need to put this on a hold for now... a lot of thing going on on my personal life... will revisit this at some point in the future. |
This Pull Request is stale because it has been open for 90 days with |
Changes
/kind enhancement
Fixes #408