mirror of
https://github.com/kata-containers/kata-containers.git
synced 2025-05-04 06:27:25 +00:00
docs: replace egrep/fgrep with grep -E/-F to avoid deprecation warning
https://lists.gnu.org/archive/html/info-gnu/2022-09/msg00001.html Signed-off-by: Balint Tobik <btobik@redhat.com>
This commit is contained in:
parent
233d15452b
commit
47140357c4
@ -198,7 +198,7 @@ it stores. When messages are suppressed, it is noted in the logs. This can be ch
|
||||
for by looking for those notifications, such as:
|
||||
|
||||
```bash
|
||||
$ sudo journalctl --since today | fgrep Suppressed
|
||||
$ sudo journalctl --since today | grep -F Suppressed
|
||||
Jun 29 14:51:17 mymachine systemd-journald[346]: Suppressed 4150 messages from /system.slice/docker.service
|
||||
```
|
||||
|
||||
|
@ -98,7 +98,7 @@ a number larger than `0` if you have either of the `vmx` or `svm` nested virtual
|
||||
available:
|
||||
|
||||
```sh
|
||||
$ minikube ssh "egrep -c 'vmx|svm' /proc/cpuinfo"
|
||||
$ minikube ssh "grep -c -E 'vmx|svm' /proc/cpuinfo"
|
||||
```
|
||||
|
||||
## Installing Kata Containers
|
||||
@ -122,8 +122,8 @@ and will be executing a `sleep infinity` once it has successfully completed its
|
||||
You can accomplish this by running the following:
|
||||
|
||||
```sh
|
||||
$ podname=$(kubectl -n kube-system get pods -o=name | fgrep kata-deploy | sed 's?pod/??')
|
||||
$ kubectl -n kube-system exec ${podname} -- ps -ef | fgrep infinity
|
||||
$ podname=$(kubectl -n kube-system get pods -o=name | grep -F kata-deploy | sed 's?pod/??')
|
||||
$ kubectl -n kube-system exec ${podname} -- ps -ef | grep -F infinity
|
||||
```
|
||||
|
||||
> *NOTE:* This check only works for single node clusters, which is the default for Minikube.
|
||||
@ -197,7 +197,7 @@ $ minikube ssh -- uname -a
|
||||
And then compare that against the kernel that is running inside the container:
|
||||
|
||||
```sh
|
||||
$ podname=$(kubectl get pods -o=name | fgrep php-apache-kata-qemu | sed 's?pod/??')
|
||||
$ podname=$(kubectl get pods -o=name | grep -F php-apache-kata-qemu | sed 's?pod/??')
|
||||
$ kubectl exec ${podname} -- uname -a
|
||||
```
|
||||
|
||||
|
@ -531,7 +531,7 @@ $ ls /dev/vfio
|
||||
* Check that the modules load when inside the Kata Container.
|
||||
|
||||
```sh
|
||||
bash-5.0# egrep "qat|usdm_drv" /proc/modules
|
||||
bash-5.0# grep -E "qat|usdm_drv" /proc/modules
|
||||
qat_c62xvf 16384 - - Live 0x0000000000000000 (O)
|
||||
usdm_drv 86016 - - Live 0x0000000000000000 (O)
|
||||
intel_qat 184320 - - Live 0x0000000000000000 (O)
|
||||
|
@ -42,7 +42,7 @@ The following is an example of how to use `lspci` to check if your NIC supports
|
||||
SR-IOV.
|
||||
|
||||
```
|
||||
$ lspci | fgrep -i ethernet
|
||||
$ lspci | grep -i -F ethernet
|
||||
01:00.0 Ethernet controller: Intel Corporation Ethernet Controller 10-Gigabit X540-AT2 (rev 03)
|
||||
|
||||
...
|
||||
|
Loading…
Reference in New Issue
Block a user