Lazy coder

Results 6 comments of Lazy coder

It's still happening to me as well with M1 shared won't work. But it's working with bridged. ```bash ❯ sudo /opt/homebrew/Cellar/socket_vmnet/1.1.1/bin/socket_vmnet --pidfile=/private/var/run/lima/shared_socket_vmnet.pid --socket-group=everyone --vmnet-mode=shared --vmnet-gateway=192.168.105.1 --vmnet-dhcp-end=192.168.105.254 --vmnet-mask=255.255.255.0 /private/var/run/lima/socket_vmnet.shared Initializing vmnet.framework...

> same here, export OBJC_DISABLE_INITIALIZE_FORK_SAFETY=YES solve the problem. I got this problem after upgrading hubspot-api-client to 10.1.1 M1 Max, Ruby 2.7.4 Rails 6.0.4

I have the same kind of requests as well. PITR is very good, before using `kubegres` we are backing up with the following strategy: * base backup of the DB...

You can `kubectl get cronjob` to get the cronjob and then `kubectl create job --from=cronjob/{you cronjob} mybackup` `kubeclt get pod` to watch the pod and debug it with `kubectl exec`...

It seems that the CronJob spec is not changed, it must be something wrong with the manager `kubectl get pod -n kubegres-system` and check the logs? or you can delete...

Add a ingress? or manually add another service as NodePort? I think inthery you should be able to add your own service there should be any conflict between them.