Data Science Lab

docker run -p 4000:80 username/repo:tag

http://localhost:4000

참고 : Windows 10과 같이 Hyper-V가 설치된 Windows 시스템을 사용하는 경우 VirtualBox를 설치할 필요가 없으므로 대신 Hyper- V를 사용해야 한다.

docker-machine create --driver virtualbox myvm1

docker-machine create --driver virtualbox myvm2

docker-machine create -d hyperv --hyperv-virtual-switch "myswitch" myvm1

docker-machine create -d hyperv --hyperv-virtual-switch "myswitch" myvm2

docker-machine ls

NAME    ACTIVE   DRIVER       STATE     URL                         SWARM   DOCKER        ERRORS

myvm1   -        virtualbox   Running   tcp://192.168.99.100:2376           v17.06.2-ce

myvm2   -        virtualbox   Running   tcp://192.168.99.101:2376           v17.06.2-ce

docker-machine ssh myvm1 “docker swarm init --advertise-addr 10.77.253.120”

$ docker-machine ssh myvm1 "docker swarm init --advertise-addr <myvm1 ip>"

Swarm initialized: current node <node ID> is now a manager.

To add a worker to this swarm, run the following command:

  docker swarm join \

  --token <token> \

  <myvm ip>:<port>

To add a manager to this swarm, run 'docker swarm join-token manager' and follow the instructions.

[Port 2377 and 2376]

항상 docker swarm init 및 docker swarm join을 포트 2377 (swarm 관리포트)과 결합 시키거나 포트를 전혀 사용하지 않고 기본값으로 설정한다. docker-machine ls 의해 반환된 컴퓨터 IP 주소는 Docker 데몬 포트인 2376을 포함한다. 이 포트를 사용하면 오류가 발생할 수 있다.

[Having trouble using SSH? Try the –native-ssh flag]

Docker Machine에는 Swarm 관리자에게 명령을 보내는데 문제가 있는 경우 사용자 시스템의 SSH를 사용할 수 있는 옵션이 있다. ssh 명령을 호출 할때 –native-ssh 플래그를 지정하면 된다.

Ex) docker-machine --native-ssh ssh myvm1 ...

docker-machine ssh myvm2 "docker swarm join --token SWMTKN-1-4ho0uf7g5lw0t1jj9i3chv364edmt1dt9q5jb1vqbhlz6li86m-ajbkydx8gees9t6hez7tmcf7y 10.77.253.120:2377"

$ docker-machine ssh myvm2 "docker swarm join \

--token <token> \

<ip>:2377"

This node joined a swarm as a worker.

docker swarm join-token worker

$ docker-machine ssh myvm1 "docker node ls"

ID                            HOSTNAME            STATUS              AVAILABILITY        MANAGER STATUS

brtu9urxwfd5j0zrmkubhpkbd     myvm2               Ready               Active

rihwohkh3ph38fhillhhb84sk *   myvm1               Ready               Active 

[Leaving a swarm]

현재 Swarm그룹에서 탈퇴 하려면 각 노드에서 docker swarm leave를 실행할 수 있다.

docker-machine env myvm1

$ docker-machine env myvm1

export DOCKER_TLS_VERIFY="1"

export DOCKER_HOST="tcp://192.168.99.100:2376"

export DOCKER_CERT_PATH="/Users/sam/.docker/machine/machines/myvm1"

export DOCKER_MACHINE_NAME="myvm1"

# Run this command to configure your shell:

# eval $(docker-machine env myvm1)

eval $(docker-machine env myvm1)

$ docker-machine ls

NAME    ACTIVE   DRIVER       STATE     URL                         SWARM   DOCKER        ERRORS

myvm1   *        virtualbox   Running   tcp://192.168.99.100:2376           v17.06.2-ce

myvm2   -        virtualbox   Running   tcp://192.168.99.101:2376           v17.06.2-ce

docker-machine env myvm1

PS C:\Users\sam\sandbox\get-started> docker-machine env myvm1

$Env:DOCKER_TLS_VERIFY = "1"

$Env:DOCKER_HOST = "tcp://192.168.203.207:2376"

$Env:DOCKER_CERT_PATH = "C:\Users\sam\.docker\machine\machines\myvm1"

$Env:DOCKER_MACHINE_NAME = "myvm1"

$Env:COMPOSE_CONVERT_WINDOWS_PATHS = "true"

# Run this command to configure your shell:

# & "C:\Program Files\Docker\Docker\Resources\bin\docker-machine.exe" env myvm1 | Invoke-Expression

& "C:\Program Files\Docker\Docker\Resources\bin\docker-machine.exe" env myvm1 | Invoke-Expression

PS C:PATH> docker-machine ls

NAME    ACTIVE   DRIVER   STATE     URL                          SWARM   DOCKER        ERRORS

myvm1   *        hyperv   Running   tcp://192.168.203.207:2376           v17.06.2-ce

myvm2   -        hyperv   Running   tcp://192.168.200.181:2376           v17.06.2-ce

docker stack deploy -c docker-compose.yml getstartedlab

참고 : 이미지가 Docker hub대신 개인 레지스트리에 저장되어 있는 경우 docker login <your-registry>을 사용하여 docker login <your-registry> 해야하며 위 명령에 –with-registry-auth 플래그를 추가해야한다.

Ex)

docker login registry.example.com

docker stack deploy --with-registry-auth -c docker-compose.yml getstartedlab

그러면 암호화된 WAL 로그를 사용하여 로컬 클라이언트의 서비스가 배포된 swarm 노드로 로그인 토큰이 전달된다. 이 정보로 노드는 레지스트리에 로그인하여 이미지를 가져올 수 있다.

docker stack ps getstartedlab

$ docker stack ps getstartedlab

ID            NAME                  IMAGE                   NODE   DESIRED STATE

jq2g3qp8nzwx  getstartedlab_web.1   gordon/get-started:part2  myvm1  Running

88wgshobzoxl  getstartedlab_web.2   gordon/get-started:part2  myvm2  Running

vbb1qbkb0o2z  getstartedlab_web.3   gordon/get-started:part2  myvm2  Running

ghii74p9budx  getstartedlab_web.4   gordon/get-started:part2  myvm1  Running

0prmarhavs87  getstartedlab_web.5   gordon/get-started:part2  myvm2  Running

[Connecting to VMs with docker-machine env and docker-machine ssh]

·         쉘을 myvm2와 같은 다른 시스템과 통신하도록 설정하려면 동일하거나 다른 쉘에서 docker-machine env를 다시 실행한 다음 주어진 명령을 실행하여 myvm2를 가리킨다. 이것은 항상 현재 쉘에만 적용된다. 구성되지 않은 쉘로 변경하거나 새 쉘을 열면 명령을 다시 실행해야 한다. docker-machine ls를 사용하여 머신을 나열하고 그들이 어떤 상태인지 파악하고 IP주소를 얻고 연결되어 있는 경우 어떤 것이 있는지 찾아본다. 자세한 내용은 아래 링크를 참고 한다.

https://docs.docker.com/machine/get-started/#create-a-machine

·         Docker명령을 docker-machine ssh <machine> “<command>” 형식으로 랩핑할 수도 있다. 이 docker-machine ssh <machine> “<command>”은 VM에 직접 기록하지만 로컬 호스트 파일에 즉시 액세스할 수 는 없다.

·         Mac및 Linux에서는 docker-machine scp <file> <machine> : ~을 사용하여 여러 컴퓨터에서 파일을 복사할 수 있지만 Windows 사용자는 Git bash와 같은 Linux 터미널 에뮬레이터가 필요하다.

이 튜토리얼은 docker-machine CLI를 통해 모든 플랫폼에서 사용할 수 있으므로 docker-machine ssh 와 docker-machine env를 모두 데모한다.

[Having connectivity trouble?]

Swarm 모드를 활성화 하기 전에 swarm에서 수신 네트워크를 사용하려면 swarm 노드간에 다음 포트를 열어야 한다.

·         컨테이너 네트워크 검색을 위한 포트 7946 TCP/UDP

·         컨테이너 수신 네트워크용 포트 4789 UDP

docker stack rm getstartedlab

[Keep the swarm or remove it?]

Swarm을 제거 하고 싶다면 아래 명령을 사용한다.

Docker-machine ssh myvm2 “docker swarm leave”

Docker-machine ssh myvm1 “docker swarm leave –f”

[Mac or Linux]

eval $(docker-machine env -u)

[Windows]

& "C:\Program Files\Docker\Docker\Resources\bin\docker-machine.exe" env -u | Invoke-Expression

docker-machine ls

$ docker-machine ls

NAME    ACTIVE   DRIVER       STATE     URL   SWARM   DOCKER    ERRORS

myvm1   -        virtualbox   Stopped                 Unknown

myvm2   -        virtualbox   Stopped                 Unknown

$ docker-machine start myvm1

Starting "myvm1"...

(myvm1) Check network to re-create if needed...

(myvm1) Waiting for an IP...

Machine "myvm1" was started.

Waiting for SSH to be available...

Detecting the provisioner...

Started machines may have new IP addresses. You may need to re-run the `docker-machine env` command.

$ docker-machine start myvm2

Starting "myvm2"...

(myvm2) Check network to re-create if needed...

(myvm2) Waiting for an IP...

Machine "myvm2" was started.

Waiting for SSH to be available...

Detecting the provisioner...

Started machines may have new IP addresses. You may need to re-run the `docker-machine env` command.

docker-machine create --driver virtualbox myvm1 # Create a VM (Mac, Win7, Linux)

docker-machine create -d hyperv --hyperv-virtual-switch "myswitch" myvm1 # Win10

docker-machine env myvm1                # View basic information about your node

docker-machine ssh myvm1 "docker node ls"         # List the nodes in your swarm

docker-machine ssh myvm1 "docker node inspect <node ID>"        # Inspect a node

docker-machine ssh myvm1 "docker swarm join-token -q worker"   # View join token

docker-machine ssh myvm1   # Open an SSH session with the VM; type "exit" to end

docker node ls                # View nodes in swarm (while logged on to manager)

docker-machine ssh myvm2 "docker swarm leave"  # Make the worker leave the swarm

docker-machine ssh myvm1 "docker swarm leave -f" # Make master leave, kill swarm

docker-machine ls # list VMs, asterisk shows which VM this shell is talking to

docker-machine start myvm1            # Start a VM that is currently not running

docker-machine env myvm1      # show environment variables and command for myvm1

eval $(docker-machine env myvm1)         # Mac command to connect shell to myvm1

& "C:\Program Files\Docker\Docker\Resources\bin\docker-machine.exe" env myvm1 | Invoke-Expression   # Windows command to connect shell to myvm1

docker stack deploy -c <file> <app>  # Deploy an app; command shell must be set to talk to manager (myvm1), uses local Compose file

docker-machine scp docker-compose.yml myvm1:~ # Copy file to node's home dir (only required if you use ssh to connect to manager and deploy the app)

docker-machine ssh myvm1 "docker stack deploy -c <file> <app>"   # Deploy an app using ssh (you must have first copied the Compose file to myvm1)

eval $(docker-machine env -u)     # Disconnect shell from VMs, use native docker

docker-machine stop $(docker-machine ls -q)               # Stop all running VMs

docker-machine rm $(docker-machine ls -q) # Delete all VMs and their disk images

Readtrace 또는 ostress 에서 GetLogicalProcessorInformation API를 사용하여 프로세서 관계를 출력

Active proc mask(0): 0x000000FF

        Architecture: 9

           Page size: 4096

                CPUs: 8

    Processor groups: 1

        Highest node: 0

  Proximity: 00  Node: 00

—————————————

               Group: 0

—————————————

        Processor(s): 0x00000003 Function units: Shared    <— 이진 값을 변경하면 논리당 2개의 프로세서를 나타냄

        Processor(s): 0x0000000C Function units: Shared    <— 프로세서는 RelationProcessorCore 를 나타냄

        Processor(s): 0x00000030 Function units: Shared

        Processor(s): 0x000000C0 Function units: Shared

        Package mask: 0x000000FF    <— 패키지는 RelationProcessorPackage 나타냄

        Processor(s): 0x000000FF assigned to Numa node: 0

MSINFO32 결과

Processor    Intel(R) Core(TM) i7-4810MQ CPU @ 2.80GHz, 2801 Mhz, 4 Core(s), 8 Logical Processor(s)

SQL Error Log

SQL Server detected 1 sockets with 4 cores per socket and 8 logical processors per socket, 8 total logical processors; using 8 logical processors based on SQL Server licensing. This is an informational message; no user action is required.

Active proc mask(0): 0x0000000F

        Architecture: 9

           Page size: 4096

                CPUs: 4

    Processor groups: 1

        Highest node: 0

  Proximity: 00  Node: 00

—————————————

               Group: 0

—————————————

        Processor(s): 0x00000001 Function units: Separated

        Processor(s): 0x00000002 Function units: Separated

        Processor(s): 0x00000004 Function units: Separated

        Processor(s): 0x00000008 Function units: Separated

        Package mask: 0x0000000F

        Processor(s): 0x0000000F assigned to Numa node: 0

MSINFO32

Processor    Intel(R) Core(TM) i7-4810MQ CPU @ 2.80GHz, 2794 Mhz, 4 Core(s), 4 Logical Processor(s)