Oracle @VirtualBox 6.1.6 now released fixes shared clipboard and other bugs
unfortunately you CANT do an inplace update because vboxnetdhcp process blocks the update so
oracle vbox bug tracker
Raspberry Pi docker
CentOS 8 & IBM Red Hat 8 support QEMU & KVM
# yum groupinstall "Virtualization Host" # yum install virt-install # yum install virt-manager # yum install libvirt-nss # systemctl enable --now libvirtd
however note that IBM Red Hat say
while QEMU is an essential component of the architecture, it is not intended to be used directly on RHEL 8 systems, due to security concerns. Therefore, using qemu-* commands is not supported by Red Hat, and it is highly recommended to interact with QEMU using libvirt.
so on centos 8 and ibm red hat 8 instead of qemu-* use these commands
$ virt-host-validate $ virt-install $ virt-manager $ virt-viewer $ virsh
See also
and red hat developers also can refer to
how to run @balena_io #kvm #qemu images
On systems with KVM support:
$ qemu-system-x86_64 -drive file=resin-image-qemux86-64.img, \ media=disk, cache=none, format=raw \ -net nic,model=virtio -net user \ -m 512 -nographic -machine type=pc, -smp 4 \ accel=kvm -cpu host
On systems without KVM support:
$ qemu-system-x86_64 -drive file=resin-image-qemux86-64.img, \ media=disk, cache=none, format=raw \ -net nic,model=virtio -net user \ -m 512 -nographic -machine type=pc -smp 4
see
quay.io is moving to cdn.quay.io
on Saturday, 25 April 2020 at 4 PM ET quay.io will be rotating the domain name returned for CloudFront based blob requests from its current domain to ‘cdn.quay.io’. If you currently whitelist the quay.io CloudFront domain name, please make sure to *add* ‘cdn.quay.io’ to your whitelistÂ
IBM Red Hat 7 UBI container images (public)
IBM Red Hat 7 UBI container images (subscription reqd)
IBM Red Hat 7 UBI os and optional repos
IBM Red Hat 8 UBI container images (public)
IBM Red Hat 8 UBI container images (subscription required)
IBM Red Hat 8 UBI BaseOS & AppStream repos
see also
redhat developers only
buildah from scratch & buildah build-using-dockerfile (bud)
build
buildah from scratch buildah from photon buildah bud -t mycontainer buildah pull registry.access.redhat.com/ubi8/ubi:latest
config
buildah config buildah copy buildah mountbuildah run
push container into an image
buildah commit build push
docker file ENTRYPOINT v CMD
buildah on github
see also
red hat developer subscribers only
ibmredhat 8 & @OpenShift #container management #devops
ibmredhat have removed the Docker container engine, along with the docker command, from Red Hat Enterprise Linux 8 entirely. For RHEL 8, Docker is not included and not supported by Red Hat (although it is still available from other sources)
with ibmredhat the focus is not on running individual containers from the command line. The primary venue for running containers is a Kubernetes-based platform, such as OpenShift.
By repositioning OpenShift as the project for running containers, container engines like Docker become just another component of OpenShift with no direct access by end users.
Because the container engine in OpenShift is not meant to be used directly, it can be
implemented with a limited feature set that focuses on doing everything that OpenShift needs, without having to implement lots of standalone features
Tools like podman, skopeo, and buildah were developed to take over those docker command features.
the newworld tools are
ibmredhat universal base image (UBI) containers
to build a container run buildah
$ buildah bud -t mycontainer Dockerfile FROM registry.access.redhat.com/ubi8/ubi ADD myecho /usr/local/bin ENTRYPOINT "/usr/local/bin/myecho" CMD "/usr/local/bin/myecho" myecho echo "This container works!"
to manage, run, stop, start a container use podman
$ podman run -i -t -p 8080:80 --name=pho photon /bin/bash
$ podman inspect --format='{{.Path}}' pho
$ podman logs pho
$ podman stop pho
$ podman start -i -a pho
to copy containers use skopeo
$ skopeo
IBM Red Hat 8 building, running & managing containers with podman & buildah
See also
