The three tools I know of for working with registries without a docker engine are crane from Google, skopeo from RedHat, and regclient from myself. The workflow that's needed is to extract the tar, push each layer and config, and then push the manifests. OCI's distribution-spec includes details on the registry API, but realize that the authentication doesn't have a spec over there (at least ...
I tried to release it like this 1, it works, but I want to implement dynamic change of parameters not of the storage, but of the cell 2. Want to implement the following logic: checking the available cells in the storage, finding XYZ an available cell and moving the crane to this coordinate.
I want that a crane moves an agent (container) to another agent (truck). Both are two types of agents. In the MoveByCrane block exits the option to choose "Destination is" to "Agent". My idea was to tell the crane here: Move the container to the truck. Each Container has a variable named v_ExitTruck in which I save a specific truck.
Unfortunately I can't find a way to push an existing tarball image with kaniko without rebuilding it. I also tried crane for the push, but can't get a login due to the non-existent credHelper. I don't actually want to do big installations, nor do I want to create a custom image for this. Is this possible? What would be potential solutions?
I already have the multi-arch image in a local registry. This is an interesting idea, but I need to be able to docker load the image into Docker engine on the target machine. Specifically, I'd like to have a single .tar file with the multi-arch image, then do docker load on the target machine, and have it load the image for the target machine's architecture (from the .tar file) into the target ...