diff --git a/DockerCommands/docker b/DockerCommands/docker index d61af2e..fd0abf6 100644 --- a/DockerCommands/docker +++ b/DockerCommands/docker @@ -1,4 +1,5 @@ Docker:-Container +test apt-get update apt-get install docker.io @@ -196,10 +197,50 @@ mysql> select * from emp; | xyz | 5555555 | +------+---------+ 1 row in set (0.00 sec) +history of docker image +docker image history image_name +Detalis information of docker image +docker image inspect image_id +delete all unused image +docker image prune +if add new slave with master +docker swarm join-token worker +join as a master +docker swarm join-token manager +left from swarm +docker swarm leave +make all slave master(docker swarm olny allow 1,3,5,7 master node) +docker node promote slave1 slave2 + +make again slave +docker node demote slave1 slave2 + +docker swarm visulizer + +attache the lable with worker node(this command run only master node) +docker node update --label-add ='ssd=true' workernode01 + +attache the replicas with label workdernpde01 +docker service create --constraint='node.labels.ssd==true' --replicas=3 -d alpine + +we can also configure engine level label(for engine leave need to configure the daemon.json file) + shift the container to other workers + docker node update --availablity=drain workert01 + +docker stack deploy:- When running Docker Engine in swarm mode, you can use docker stack deploy to deploy a complete application stack to the swarm. +The deploy command accepts a stack description in the form of a Compose file. The docker stack deploy command supports any Compose file of version “3.0” or above. +stack file:- + From the Cloud stack file YAML reference, it states a stack file is a file in YAML format that defines one or more services, similar to a docker-compose.yml file but with a few extensions. + + docker stack deploy -c docker-compose.yml wordpresstack + +* docker restart command for start the again ccontainer +- docker start container_id +- docker container run -d --restart unless-stop imagename