buildx | Docker CLI plugin for extended build capabilities | Continuous Deployment library

You can run docker buildx ls to list the builders and docker buildx use to set the the current instance (or the default one with the --default flag). The config files for builders are located in ~/.docker/buildx/instances, I believe, at least in Docker version 20.10.5.

As you can see in your error :

Can't find google.com

Container does't have access to network and therefore it can't find google !

And I can't see your Dockerfile and docker-compose.yml (If you use it) in the question above !

BUT

First step it's better to create a network using docker network create --help

--help ------> For seeing which options you want to use for your container networking :) (according to docs.docker)

Second step it's to EXPOSE: the port on docker file (docs.docker & Article about concept of EXPOSE)

AND LAST : Try to check your container networking another way and simply use docker run

Try to use bash in your main image That is Cent OS for checking the network of container

Docker automatically defines a set of ARGs for you when you're using the BuildKit backend (which is now the default). You need to declare that ARG, and then (within the RUN command) you can use an environment variable $TARGETOS to refer to the target operating system (the documentation suggests linux or windows).

Buildx runs builds within a separate container, not directly in your docker engine. And the output of buildx does not store the resulting image in the local docker engine. This doesn't work when you get into multi-platform images anyway, so you typically push directly to the registry. It's much more efficient to avoid moving layers around that didn't change in the registry, and allows you to manage multi-platform images (everything loaded into the docker engine is dereferenced to a single platform).

If you really want to save the output to the local docker engine, you can use --load in the buildx command. However, the preferred option is to use the build-push-action that builds your tag directly and pushes it in one step. This would mean reordering your steps to determine the versions and other variables first, and then run the build against that. You can see an example of this in my own project which was assembled from various other docker examples out there.

Here's a quick untested attempt to make that change:

I solved my problem with shell tool yq

Actually, I figured it out. Have to add build-args to the Build and Push part, and remove the env from there.

So instead of:

The domain is ghcr.io (short for GitHub Container Registry), not ghrc.io. This is a typo and you're trying to push your container image to an unknown host on the internet.

That problem was in the hosting provider.

Provider told us that other customers have tried to configure Docker Swarm on their VPS too, but no one has figured out how to get it to work.

The provider didn't allow any kernel modification or anything else on the lower level.

Now we are using another hosting provider and everything works fine.