As the pod starts with an empty persistent volume there is nothing there. No previous instance. Nothing. That's why I am wondering... _______________________________________________ 389-users mailing list -- 389-users@lists.fedoraproject.org To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
- [389-users] 389DS on K8s - dirserv won't start Ronald Wimmer
- [389-users] Re: 389DS on K8s - dirserv won't start Mark Reynolds
- [389-users] Re: 389DS on K8s - dirserv won't start Ronald Wimmer
- [389-users] Re: 389DS on K8s - dirserv won't start Viktor Ashirov
- [389-users] Re: 389DS on K8s - dirserv won't start Ronald Wimmer
- [389-users] Re: 389DS on K8s - dirserv won't s... Ronald Wimmer
- [389-users] Re: 389DS on K8s - dirserv won't s... Viktor Ashirov
- [389-users] Re: 389DS on K8s - dirserv won... Ronald Wimmer
- [389-users] Re: 389DS on K8s - dirser... Viktor Ashirov
- [389-users] Re: 389DS on K8s - di... Ronald Wimmer
- [389-users] Re: 389DS on K8s ... Viktor Ashirov