kubevirt
In labs, replace wget with curl, as wget isn't available OOTB in common linux flavours
Description: As wget isn't present OOTB in linux flavours like RHEL, when lab1 first command is executed (wget https://kubevirt.io/labs/manifests/vm.yaml), got error "wget: command not found". Also wget is used in lab2 as detailed in Additional context section below.
What you expected: Download to work always. So, as curl is more standardly available across linux flavours than wget, replace wget with curl across all labs.
URL:
- https://kubevirt.io/labs/kubernetes/lab1.html
- https://kubevirt.io/labs/kubernetes/lab2.html
Additional context:
In lab2 also, I see usage of wget at places along with curl usage: ex:
Let’s create a Virtual Machine making use of it. Review the file vm1_pvc.yml.
Copy wget https://kubevirt.io/labs/manifests/vm1_pvc.yml
My OS details, where wget isn't present:
[root@vm1 ~]# cat /etc/os-release NAME="Red Hat Enterprise Linux" VERSION="9.4 (Plow)" ID="rhel" ID_LIKE="fedora" VERSION_ID="9.4" PLATFORM_ID="platform:el9" PRETTY_NAME="Red Hat Enterprise Linux 9.4 (Plow)" ANSI_COLOR="0;31" LOGO="fedora-logo-icon" CPE_NAME="cpe:/o:redhat:enterprise_linux:9::baseos" HOME_URL="https://www.redhat.com/" DOCUMENTATION_URL="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9" BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Red Hat Enterprise Linux 9" REDHAT_BUGZILLA_PRODUCT_VERSION=9.4 REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux" REDHAT_SUPPORT_PRODUCT_VERSION="9.4" [root@vmx1 ~]#
Hi @prasad89,
I have already started looking on this as @chandramerla asked to work
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
/lifecycle rotten
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
/close
@kubevirt-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity. Reopen the issue with
/reopen. Mark the issue as fresh with/remove-lifecycle rotten./close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.