I had to monitor the execution of N containers that were collecting data from multiple accounts at IBM Cloud. Here, each container is simulation the process to collect the data, one container per account:
If you see an error like the above one during your Tekton deployment, you can use the steps provided here to fix it. Issue: Solution:
The world is multi-arch and you can easily leverage it!
If you need to delete running containers based on their lifetime, this handy combination of commands can help you. It deletes all containers running for more than 2 hours. HOUR=2docker ps –filter “status=running” | grep hours | awk ‘{if ($4 >=$HOUR) print $1,”must be deleted”; system(“docker rm -f ” $1)}’
If you need to test a custom version of grub2 you can follow the steps bellow to build the necessary packages for RHEL8 (it should also work on CentOS and Fedora):
To build GitLab Runner for ppc64le you can run the following steps in a x86_64 machine with Ubuntu 20.04:
creating a new CentOS8 .ova image for PowerVS without a PowerVC 🙂
As part of an automation I had to collect only the name and size of the multi-path devices attached to a given VM. Here is the result: multipath -ll | sed -n ‘/^mpath/,/^size/p’ >> /tmp/mpath.log && x=1 && while IFS=”” read -r p || [ -n “$p” ]; do STR1=$(printf ‘%s\n’ “$p” | sed ‘s/\s.*$//’);… Continue reading linux: pretty printing multi-path device name and size
nullpointerexception 