Control Center in Windows 10 and Podman

I have a question about how I install control center using podman emulating docker and Kind.
I have many days trying and I declare myself incompetent to do this task.I haven’t had any success with this. I’ve tried ChatGPT and DeepSeek, but I can’t seem to get it right. May be anyone can help me please.

Hi, thank you for the question. We have not tested this with Podman, so cannot guarantee it will work.

However, if you want to try manually running the yaml files, you can generate them via the template helm command. You can take your install command, replace install with template, and add the --dry-run and --debug flags, for example:

helm template control-center oci://docker.io/vaadin/control-center -n control-center --create-namespace --set user.email=example@example.com --set domain=example.com --dry-run --debug

Thank you.
I Have a progress, Now I’m have this problem.
:pushpin: NOTE: Please do not close this terminal as this process must stay alive for the tunnel to be accessible …

:exclamation: Access to ports below 1024 may fail on Windows with OpenSSH clients older than v8.1. For more information, see: Accessing apps | minikube
:running_man: Starting tunnel for service control-center-ingress-nginx-controller.
:exclamation: Access to ports below 1024 may fail on Windows with OpenSSH clients older than v8.1. For more information, see: Accessing apps | minikube
:exclamation: Access to ports below 1024 may fail on Windows with OpenSSH clients older than v8.1. For more information, see: Accessing apps | minikube
:running_man: Starting tunnel for service control-center.
:running_man: Starting tunnel for service control-center-keycloak-ingress.

I install the last version sh in choco but don’t work.

From the log, it looks like a tunnel is created for each service. Does this mean that they are being exposed on different ports?

Check on which port the tunnel is exposing control-center-ingress-nginx-controller. If it’s not 443, then you may have to specify it in the address (e.g. https://control.local:8443). There may still be a problem with the login, since it redirects to the auth.local address, which would need to use the same port number.

currently it is like this:

That looks good. I would go about analyzing why the service is not available.

Follow the troubleshooting guide here: Troubleshooting for Vaadin Control Center

Oh I just noticed that the status of the control-center pod is Init:ImagePullBackOff. This probably means it can’t reach the image repository, which in this case is Docker Hub. If you follow the instructions in the guide I linked above, you should see something to that effect in the event log.

The issue has resolved.

1 Like