installing cdk locally via minikube not working
#667
Comments
|
I am facing the exact same problem. |
|
@luiscvega @dhruvdave-iv I have this occasionally as well, and the standard advice from our developers is to just run the script a second time, and usually it works. If it doesn't try running it again. I have a suspicion it might be due to slow download speeds getting the Docker images down to the Docker repository on Minikube when my Internet speed is slow. I've been working from home since Covid started; never used to have this problem when working from an office. How is your connection speed - might that be a source of the problem? One thing you could try is to |
|
@luiscvega @dhruvdave-iv I just ran a test where I pulled the Docker images after I ran cdk-minikube, and before I ran forgeops install. It ran in 8 minutes with no timeouts. From the release/7.2.0 branch, my steps were: Could you please try to replicate this, and let me know if it you avoid the timeouts (and how long it took to run forgeops install)? If it does, I'll either update the cdk-minikube script to automatically prime the Minikube docker repo, or I'll add steps to the documentation to tell users to do it manually. |
|
@dgoldssfo , I tried the steps you suggested, still the same error. I did a bit more troubleshooting and found that ds-operator is failing to update the password. Bellow are the logs: {"level":"info","ts":1675070210.6966136,"logger":"controller-runtime.metrics","msg":"metrics server is starting to listen","addr":":8080"} |
|
@luiscvega @dhruvdave-iv Are both of you attempting this on Linux? Could you say a little more about your environment or run the bin/debug-logs script (in the forgeops repo) and post the results here? I haven't been able to duplicate this on macOS so far, so maybe it's something OS-specific. I'll see if I can grab a Linux laptop tomorrow and have at it. |
|
It works! I pulled the images first before running it all over again. Although, I'm not sure if this is actually what fixed it. @dgoldssfo, can you confirm that this flow is not using any other external services? Probably not related but I also added the In any case, I am very grateful for the assistance, @dgoldssfo. I am using Ubuntu 22.04.1 LTS. I'll keep this open for now just in case @dhruvdave-iv still needs assistance. @dhruvdave-iv, what steps are you running? You can check my commands below and see if it will work. |
|
@luiscvega Yeah, it's self-contained. The forgeops install command checks to se if additional services the deployment relies on (like cert-manager and a couple of operators) are already there, and. if they are not, it installs them. I'm reasonably certain that pre-loading the images fixed your problem, and I'm thinking of adding the docker pulls to the cdk-minikube command. If you have an even somewhat slow internet connection, long docker pulls can cause timeouts in forgeops install. |
|
@dhruvdave-iv I'll have another look if you can send me more details about your deployment environment, the stuff I suggested earlier. It's much easier to troubleshoot these kinds of problems if you can send me the debug-logs output instead of just some logs (or just stdout). Here's what we ask ForgeRock customers to send when they encounter a problem: https://backstage.forgerock.com/docs/forgeops/7.2/start/support.html#problem_reports_and_information_requests Speaking of which, if you're a customer, you could file a support ticket and might get an answer more quickly. |
|
I did a clean install again and getting the same error. Attached is the output of the forgeops/bin/debug-logs. dhruv@ubuntu: |
|
Thanks for sending the diagnostics, @dhruvdave-iv. Our engineers are going to look at it - they've seen this problem before sporadically and are going to see if they can get to the bottom of it. |
|
Thanks @dgoldssfo. I noticed that the ds deployment is using us-docker.pkg.dev/forgeops-public/images/ds:7.2.0 image instead of gcr.io/forgerock-io/ds-empty:7.2.0 or gcr.io/forgerock-io/ds:7.2.0. And these images have different sha and size. Not sure if this has any bearing on this issue. |
|
Regarding the initial error, |
|
Does anyone managed to install |
|
@andylow I have installed it on Windows 11 desktop with Docker Desktop. But you have to put a Linux VM down. Check this out at 3:15. https://community.forgerock.com/t/forgeops-how-to-spin-up-a-minikube-on-your-local-device/2875 |
|
@chicodeme Thanks a lot, unfortunately, due to organization policy, I'm not allow to use any VM including Linux VM. |
|
@andylow awesome! |
I'm currently trying to follow the instructions in Cloud Developer's Kit (CDK) locally using
minikube. I am using the branch atreleases/7.2.0. I was able to start the minikube (./cdn-minikube start), able to create a namespace and added theminikube ipto/etc/hosts. However, I'm running into a few issues:Attempt 1: Install "all"
When I try to run
./foregeops install --cdk --fqdn cdk.example.com, it times out after 600 seconds. Kindly see the commands below:As you can see, the pod is running but it still times out.
Attempt 2: Staged install
So I attempted to do an install component by component. Following the instruction, I first installed
base, and thends. However, when I installam, I'm getting several of the following error from the logs:I have also tried to increase the CPUs to
4and RAM to12gbut I'm still running into the these issues.Is there a step I'm missing to run the CDK locally?
The text was updated successfully, but these errors were encountered: