If by "toolboxes" you mean the original "CoreOS Toolbox" (https://github.com/coreos/toolbox https://github.com/coreos/toolbox) which was originally a bash scrip

If by "toolboxes" you mean the original "CoreOS Toolbox" (https://github.com/coreos/toolbox https://github.com/coreos/toolbox) which was originally a bash script, now re-written in Go (https://github.com/containers/toolbox https://github.com/containers/toolbox) that's very, very unfortunate. It should just be a user configuration. In the original we defaulted to the latest Fedora image (yes, even in the days of CoreOS... blame me for that), but allowed the user to override this with an environment variable (and later a `.toolboxrc` file in their home directory). Thus, IMHO, this is a regression. Now it seems the new stewards are trying to be "clever" and protect you from yourself, creating "foot-guns" in the process. According to the docs (https://github.com/containers/toolbox#image-requirements https://github.com/containers/toolbox#image-requirements): Since Toolbox only works with OCI images that fulfill certain requirements, it will refuse images that aren't tagged with com.github.containers.toolbox="true" and com.github.debarshiray.toolbox="true" labels. These labels are meant to be used by the maintainer of the image to indicate that they have read this document and tested that the image works with Toolbox. You can use the following snippet in a Dockerfile for this: LABEL com.github.containers.toolbox="true" edit: I forgot part of my point: This is a regression from the original utility.