Docker Community Forums

Share and learn in the Docker community.

Docker-compose error on UP command

Hello

I am currently trying to start multiple containers using docker-compose, but I am having errors that I cannot resolve.

1 - I did not write this docker composes nor the images and everything works on other machines.
2 - The images are only available locally.

Here is what I was told to do.
docker load -i image.tar
docker load -i …
… (this for all images)

then when i type the command:
docker-compose up

An error message appears:
Pulling {image} ({image}: 1.15) …
ERROR: The image for the service you’re trying to recreate has been removed. If you continue, volume data could be lost. Consider backing up your data before continuing.

I tried looking on the internet docker-compose pull, but all my images are in error.

1 - Why if my images are present (displayed) when I do a docker images docker-compose trying to do a pull of these images?

I changed the command docker load -i image.tar to docker image import image.tar {image}: 1.15, but no change noticed.

2 - Could someone help me?

You might be seeing this error because you’re using the wrong Compose file version. Either specify a version of “2” (or “2.0”) and place your service definitions under the services key, or omit the version key and place your service definitions at the root of the file to use version 1.

I apologize for the slowness of the response, but there is no time for me to deal with this problem for you.

A version is defined in the “docker-compose.yml” file
version: ‘3.4’

The installation of docker is a bit special because the version is imposed on us by the customer. So I didn’t do an apt-get to install docker.

Method used for docker installation:

apt-get install apt-transport-https ca-certificates curl gnupg-agent software-properties-common
curl -fsSL {nolink-http}://download.docker.com/linux/debian/gpg | apt-key add -
apt-key fingerprint 0EBFCD88
add-apt-repository “deb [arch=amd64] {nolink-http}://download.docker.com/linux/debian $(lsb_release -cs) stable”
apt-get update
apt-get install docker-ce=17.12.1~ce-0~debian containerd.io

Method used for installing docker-compose:

curl -L “{nolink-http}://github.com/docker/compose/releases/download/1.27.4/docker-compose-(uname -s)-(uname -m)” -o /usr/local/bin/docker-compose

I will try to explain this to you because I think there is a problem here:

image: actia/das_cas:1.15
container_name: das-cas_${DAS_TAG}

but i have trouble understanding the difference between:
name and repository (and yes, I am at level 0 of docker understanding. Sorry.)

Once again lewish95 the Let me Google that for you bot has committed plagiarism. (ref)

I just spoke to a theorist (great theoretical knowledge but he does not know the exatct commands to perform)

he tells me that there is a “registry” in the docker deployment in the VM and at the client.
So, you have to change the configuration of the “docker-compose.yml” file.