Hi all, Back in late November we merged https://review.opendev.org/c/starlingx/config-files/+/865329 which removed the default docker network bridge as in some install sites the default IP address was colliding with an address already in use in their network.  StarlingX no longer runs containers with docker, so there was no functional impact to the platform itself. However, it does mean that it's no longer possible to build docker images on bare metal on StarlingX nodes.  That said, it should be possible to work around this by creating a Kubernetes pod using a suitable container image, obtaining a shell within that pod, and running docker within the container. Chris