Docker compose reports an error and multiple containers conflict
When the vulnerability repeats, I want to open the vulnerability environment. The docker compose result reports an error. I understand that it is a multi container conflict problem
The error contents are as follows:
WARNING: Found orphan containers (unacc_slave_1, unacc_master_1) for this project. If you removed or renamed this service in your compose file, you can run this command with the --remove-orphans flag to clean it up.
unacc_web_1 is up-to-date
The solution given by the system here is: – remove orphans, but it will directly delete the container, which is obviously not very good
Learned that each configuration has a project name. If you provide the - P
flag, you can specify the project name. If no flag is specified, compose
uses the current directory name.
Use the following command to specify a container name
docker-compose -p xxx up -d
Open the 8086 port specified here in the container to successfully open the mirror environment.
Read More:
- CONDA reports an error: conflict package conflict
- The docker copies the win10 host file into the docker container. An error is reported: copying between containers is not supported
- An error occurred trying to connect: get http: / / var / run/ docker.sock/v1 .21/containers/json?all
- Solve the problem of docker error: Unsupported compose file version: 3.2
- docker-compose Error Traceback (most recent call last)
- Docker starts the image and reports an error. Iptables failed: iptables — wait – t NAT – a docker – P TCP
- Docker starts MySQL container and reports an error driver failed programming external connectivity on endpoint mysq
- Docker command error during connect: get http://2F2F.2Fpipe2Fdocker_ engine/v1.36/containers/json: open//.
- Spring boot integrates Mongo to solve some common connection and permission problems. Docker compose installs Mongo
- Mac computer logs into docker and reports an error
- Docker error response from daemon: Conflict: unable to deletexxxxx
- Docker delete error response from daemon: Conflict: unable to delete xxxxx solution
- There is an unhandled exception at: 0xc0000005: an access conflict occurred while reading location 0x00000000.
- The echots in Vue reports an error. After obtaining the DOM element, the chart can be displayed. The console still reports an error
- Hadoop reports an error. Cannot access scala.serializable and python MapReduce reports an error
- The file server reports an error of 413, and the file uploaded by nginx reports an error of 413 request entity too large
- HTML method IE8 reports an error, IE8 jQuery Ajax obtains static resources reports an error, typeerror denies access
- Lamdba in the studio part reports an error. Observe lamdba reports an error but can run
- 0xc0000005: an access conflict occurred while reading location 0x00000020
- Opencv: 0xc0000005: an access conflict occurred while reading location 0x0000000010