On 30/06/2020 12:02, Ankur Sinha wrote:
On Tue, Jun 30, 2020 02:23:00 -0400, Neal Gompa wrote:
> On Tue, Jun 30, 2020 at 2:22 AM Julen Landa Alustiza
> <jlanda(a)fedoraproject.org> wrote:
>> 20/6/26 11:32(e)an, David Kirwan igorleak idatzi zuen:
>>> Hi all,
>>> If we are moving towards openshift/kubernetes backed services, we should
>>> probably be sticking with containers rather than Vagrant. We can use CRC
>>>  (Code Ready Containers) or minikube  for most local dev work.
>> In my experience CRC is a pita for occasional contribution on different
>> projects due to it's one month lifecycle. It's fine if you are using it
>> daily but if you are using for just some few projects that only need
>> some ocassional coding having to redeploy the minicluster every time is
>> hard and time consuming.
> I cannot run CRC on my laptop, full stop. I don't have enough RAM for it.
A note: running minikube on Fedora wasn't trivial the last time I'd
tried it either, on account of us aggressively pushing Podman to our
users, the minikube driver for which is still "experimental".
I can confirm this. I was trying
to run vagrant machine with minikube
and ended up with using F30 to avoid some issues in newer Fedoras.
The Kubernetes stuff we use at work on our Google Cloud instance all
relies on Docker, not Podman, so I had to figure out how to install
Docker on Fedora 32 which was another PITA. A recent fedora magazine
post helps now:
I'm still developing using Podman myself. I just haven't had the time to
get minikube + Docker working again. If folks do use it, please document
the setup somewhere. I'm sure a lot of Fedora 32 users would really
appreciate it :)
infrastructure mailing list -- infrastructure(a)lists.fedoraproject.org
To unsubscribe send an email to infrastructure-leave(a)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
Role: Fedora CPE Team - Software Engineer