Welcome to the Linux Foundation Forum!

[linkerd] where to pass the flag `--set proxyInit.runAsRoot=true`?

Hello,
The pre-checks say: "There are nodes using the docker container runtime and proxy-init container must run as root user. Try installing linkerd via --set proxyInit.runAsRoot=true"
But when I run the install script with:

  1. curl -sL run.linkerd.io/install > linkerd-install.sh
  2. sudo ./linkerd-install.sh --set proxyInit.runAsRoot=true

the same happens.
Maybe it takes to install Linkerd on the cloud? My cluster runs in virt-manager with 2 nodes

Welcome!

It looks like you're new here. Sign in or register to get started.
Sign In

Best Answers

Answers

  • Same on aws:

    1. ubuntu@cpnode:~$ curl -sL run.linkerd.io/install | sh
    2. Downloading linkerd2-cli-stable-2.11.2-linux-amd64...
    3. % Total % Received % Xferd Average Speed Time Time Time Current
    4. Dload Upload Total Spent Left Speed
    5. 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
    6. 100 44.7M 100 44.7M 0 0 6348k 0 0:00:07 0:00:07 --:--:-- 7091k
    7. Download complete!
    8.  
    9. Validating checksum...
    10. Checksum valid.
    11.  
    12. Linkerd stable-2.11.2 was successfully installed 🎉
    13.  
    14.  
    15. Add the linkerd CLI to your path with:
    16.  
    17. export PATH=$PATH:/home/ubuntu/.linkerd2/bin
    18.  
    19. Now run:
    20.  
    21. linkerd check --pre # validate that Linkerd can be installed
    22. linkerd install | kubectl apply -f - # install the control plane into the 'linkerd' namespace
    23. linkerd check # validate everything worked!
    24. linkerd dashboard # launch the dashboard
    25.  
    26. Looking for more? Visit https://linkerd.io/2/tasks
    27.  
    28. ubuntu@cpnode:~$ export PATH=$PATH:/home/ubuntu/.linkerd2/bin
    29. ubuntu@cpnode:~$ linkerd check --pre
    30. there are nodes using the docker container runtime and proxy-init container must run as root user.
    31. try installing linkerd via --set proxyInit.runAsRoot=true

    But a simple service exposed doesn't seem to work neither...

  • Now I get:

    1. ‼ cluster networks can be verified
    2. the following nodes do not expose a podCIDR:
    3. wnode
    4. see https://linkerd.io/2.11/checks/#l5d-cluster-networks-verified for hints

    but since only calico sets the pod Cidr, the worker node can't expose one?

  • Hi @chrispokorni
    Of course, calico have more options than just setting a Cidr. Thank you for the link

  • Hi @alihasanahmedk
    Great, thank you for your help

  • Always welcome @thomas.bucaioni

Welcome!

It looks like you're new here. Sign in or register to get started.
Sign In

Welcome!

It looks like you're new here. Sign in or register to get started.
Sign In

Categories

Upcoming Training