Update deploy-development-rp.md (#3359)

This is to give a heads up that this podman issue can occur if the podman user socket is not enabled.
This commit is contained in:
Anshul Verma 2024-01-21 23:48:20 +05:30 коммит произвёл GitHub
Родитель 3abcd30e5b
Коммит 922c77d1fb
Не найден ключ, соответствующий данной подписи
Идентификатор ключа GPG: B5690EEEBB952194
1 изменённых файлов: 2 добавлений и 0 удалений

Просмотреть файл

@ -123,6 +123,8 @@
By default, a public cluster will be created. In order to create a private cluster, set the `PRIVATE_CLUSTER` environment variable to `true` prior to creation. Internet access from the cluster can also be restricted by setting the `NO_INTERNET` environment variable to `true`.
> __NOTE:__ If the cluster creation fails with `unable to connect to Podman socket...dial unix ///run/user/1000/podman/podman.sock: connect: no such file or directory`, then you will need enable podman user socket by executing : `systemctl --user enable --now podman.socket`, and re-run the installation.
[1]: https://docs.microsoft.com/en-us/azure/openshift/tutorial-create-cluster
1. The following additional RP endpoints are available but not exposed via `az