No
Perhaps it will be supported in the future, but not at the moment because the use case is not very common.
Docker Release Notes: https://docs.docker.com/release-notes/
If you find that accessing github.com
is slow or failed, you can try to switch a mirror source.
# 1. install docker
curl -fsSL https://get.docker.com | bash -s docker --mirror Aliyun
# 2. install docker-compose by using curl.
# if it's very slow, you'd better use the next solution.
curl -L https://github.com/docker/compose/releases/download/1.27.2/docker-compose-`uname -s`-`uname -m` > /usr/local/bin/docker-compose
chmod +x /usr/local/bin/docker-compose
# 3. install docker-compose by using pip3
pip3 install --upgrade pip
pip3 install docker-compose
# 4. install docker-compose by using yum
# pay attention to using at least version 1.20 or higher. Using a lower version may result in a failed compose.
yum install -y docker-compose
Docker Desktop
Installation of mac is here : https://docs.docker.com/desktop/release-notes/#4242 (you can choose any version).
Check the Docker status by running the command docker info
. If it is not running, you need to start Docker first.
# Check Docker Status.
sudo systemctl status docker
# Start Docker.
sudo systemctl start docker
failed programming external connectivity … iptables: No chain/target/match by that name
service docker restart
iptables -L
Compose failed, and the prompt for the docker-compose command appeared when do compose. #5
The reason for the error is that your docker-compose version is too low. It is recommended to upgrade your docker-compose version. Issues#5
# upgrade to 1.27.2
curl -L https://github.com/docker/compose/releases/download/1.27.2/docker-compose-`uname -s`-`uname -m` > /usr/local/bin/docker-compose
chmod +x /usr/local/bin/docker-compose
You should use the docker inspect
command to find the ip of container.
docker inspect sparrow_container_test_go
If you've tried various methods and still encounter authentication failures, then delete your local data mount directory, for example, delete the directory sparrow/mongodb/data
.
- https://stackoverflow.com/questions/59274734/where-is-mongodb-config-file-located-when-running-not-as-an-ubuntu-service
- https://stackoverflow.com/questions/34559557/how-to-enable-authentication-on-mongodb-through-docker
- https://stackoverflow.com/questions/4881208/how-to-secure-mongodb-with-username-and-password
- https://stackoverflow.com/questions/37372684/mongodb-3-2-authentication-failed
- https://stackoverflow.com/questions/60394290/mongo-db-docker-image-authentication-failed
Maybe you missed the following steps.
- delete
/.env
file - must add
ssdb
service toENABLE_SERVICE_LIST
in th/.work/config/.env.amd64{arm64}
file.
You must follow the steps of How to Create New Service, youcan't skip any step.
Firstly, search the error message on the ssdb project of github.
Now, you will find the error from app_args.work_dir
, so search work_dir
int the conf file.
Finally, you already find the reason, just go to midify the work_dir
to correct path.