search

chldydgh4687 / 00Self-Linux_trial_and_error

Linux & DeepLearning
0 stars 0 forks source link

[Tip] 도커 설명서 (작성중..) #30

Open chldydgh4687 opened 4 years ago

chldydgh4687 commented 4 years ago

도커 설치를 위한 curl 설치

$ sudo apt-get install -y curl

도커 설치

$ curl -fsSL https://get.docker.com/ | sudo sh

도커 권한 부여

$ sudo usermod -aG docker $USER #현재 접속중인 사용자에게 권한주기 $ sudo usermod -aG docker your-user #your-user 사용자에게 권한주기

컨테이너 명령어

$ docker ps -a

$ docker rm (컨테이너ID or 이름)

$ docker rm -v $(docker ps -a -q -f status=exited)

서버를 위한 OS 복제

  1. 서버 이미지화 시키기 
    $ sudo su
# tar --numeric-owner --exclude=/proc --exclude=/sys -cvf linux_18.04_server_org.tar /
  2. docker 서버로 tar 파일을 복사 후 docker에 import
    • 오래기달리기.. cat의 명령줄을 치면 아래와 같은 결과가 나옴. 
      
# cat linux_18.04_server_org.tar | docker import - linux_18.04_server_org linux_18.04_server_org

sha256:9317820ec092145201488f9b5686093407b4fcb939cabbff39631ba3afac07c9

3. import 정상 확인

docker run -i -t linux_18.04_server_org /bin/bash


---

## docker hub에 이미지 보내주기

$ docker tag (이미지 이름) (계정정보)/(repository):(hub에 생성할 이름)
ex) docker tag linux_18.04_server_org chldydgh4687/ivcl_server:linux_18.04_server_org

$ docker push (계정정보)/(repository):(hub에 생성한 이름)
ex) docker push chldydgh4687/ivcl_server:linux_18.04_server_org

---

## docker hub에서 이미지 불러오기

$ docker pull (계정정보)/(repository):(hub에 있는 이미지 이름)

ex) docker pull chldydgh4687/ivcl_server:linux_18.04_server_org

---

## docker 이미지 확인

$ docker images  

## docker 이미지 삭제

$ docker rmi (이미지이름) or (이미지_id)

## 이미지 pull 이후 사용하기

$ docker run -it --name (원하는이름) (이미지 repository) /bin/bash
- /bin/bash : 해당 컨테이너의 bash shell을 실행(dockfile)  
ex) docker run -it --name yhchoi linux_18.04_server_org /bin/bash

## exit 하고 빠져나와서 다시 시작할 때  

$ docker restart yhchoi  
$ docker attach yhchoi  
$ docker restart (이전에 지정했던 이름)  

---

## 이미지 덮어쓰기 (하고있는 중..!)
chldydgh4687 commented 4 years ago

Reference link

https://subicura.com/2017/01/19/docker-guide-for-beginners-1.html
https://nicewoong.github.io/development/2017/10/09/basic-usage-for-docker/

chldydgh4687 commented 4 years ago

push 과정

image image image

chldydgh4687 commented 4 years ago

연구실 서버 설계

image

문제점 : 본 서버 cuda를 아나콘다에 연결시켰는데 해당 container 안에서 아나콘다가 실행이 안되서 anaconda에 연결되있는 cuda를 찾지를 못함..

chldydgh4687 commented 4 years ago

현재 상황

chldydgh4687 commented 4 years ago

다른 USER에서 SSH를 통해서 ANACONDA를 못찾는 오류였음.

1. SSH 서버에 접속

2. 다음의 명령어로 CONDA를 찾아서 실행

$ source /home/ivcl/anaconda2/etc/profile.d/conda.sh
$ conda activate (생성한 환경)

그래도 똑같은 오류이므로 원격서버의 bashrc의 cuda path 를 몰라서 그러는듯...(해결중..)

chldydgh4687 commented 4 years ago

새로 만든 유저의 ~/.bashrc 파일의 export 값을 설정

export PATH=/usr/local/cuda-9.0/bin${PATH:+:${PATH}} export LD_LIBRARY_PATH=/home/ivcl/anaconda2/lib export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/home/ivcl/caffe/distribute/lib export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/home/ivcl/caffe/lib export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/lib export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/cuda-9.0/lib64 export PYTHONPATH=/home/ivcl/caffe/python export PYTHONPATH=$PYTHONPATH:/home/ivcl/anaconda2/envs/ai/lib/python2.7 export PYTHONPATH=$PYTHONPATH:/USR/LOCAL/LIB/PYTHON2.7

chldydgh4687 commented 4 years ago

원격 ssh 권한 에러

chldydgh4687 commented 4 years ago

Dockerfile 작성하는 법을 알아야됨..!! 이 안에서 bashrc처럼 아나콘다 path값을 주면 문제가 없을뜻함..! caffe 또한 다시 make 해야할뜻..

$sudo vi ~/.bashrc

# ~/.bashrc: executed by bash(1) for non-login shells.
# see /usr/share/doc/bash/examples/startup-files (in the package bash-doc)
# for examples

# If not running interactively, don't do anything
[ -z "$PS1" ] && return

# don't put duplicate lines in the history. See bash(1) for more options
# ... or force ignoredups and ignorespace
HISTCONTROL=ignoredups:ignorespace

# append to the history file, don't overwrite it
shopt -s histappend

# for setting history length see HISTSIZE and HISTFILESIZE in bash(1)
HISTSIZE=1000
HISTFILESIZE=2000

# check the window size after each command and, if necessary,
# update the values of LINES and COLUMNS.
shopt -s checkwinsize

# make less more friendly for non-text input files, see lesspipe(1)
[ -x /usr/bin/lesspipe ] && eval "$(SHELL=/bin/sh lesspipe)"

# set variable identifying the chroot you work in (used in the prompt below)
if [ -z "$debian_chroot" ] && [ -r /etc/debian_chroot ]; then
    debian_chroot=$(cat /etc/debian_chroot)
fi

# set a fancy prompt (non-color, unless we know we "want" color)
case "$TERM" in
    xterm-color) color_prompt=yes;;
esac

# uncomment for a colored prompt, if the terminal has the capability; turned
# off by default to not distract the user: the focus in a terminal window
# should be on the output of commands, not on the prompt
#force_color_prompt=yes

if [ -n "$force_color_prompt" ]; then
    if [ -x /usr/bin/tput ] && tput setaf 1 >&/dev/null; then
        # We have color support; assume it's compliant with Ecma-48
        # (ISO/IEC-6429). (Lack of such support is extremely rare, and such
        # a case would tend to support setf rather than setaf.)
        color_prompt=yes
    else
        color_prompt=
    fi
fi

if [ "$color_prompt" = yes ]; then
    PS1='${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$ '
else
    PS1='${debian_chroot:+($debian_chroot)}\u@\h:\w\$ '
fi
unset color_prompt force_color_prompt

# If this is an xterm set the title to user@host:dir
case "$TERM" in
xterm*|rxvt*)
    PS1="\[\e]0;${debian_chroot:+($debian_chroot)}\u@\h: \w\a\]$PS1"
    ;;
*)
    ;;
esac

# enable color support of ls and also add handy aliases
if [ -x /usr/bin/dircolors ]; then
    test -r ~/.dircolors && eval "$(dircolors -b ~/.dircolors)" || eval "$(dircolors -b)"
    alias ls='ls --color=auto'
    #alias dir='dir --color=auto'
    #alias vdir='vdir --color=auto'

    alias grep='grep --color=auto'
    alias fgrep='fgrep --color=auto'
    alias egrep='egrep --color=auto'
fi

# some more ls aliases
alias ll='ls -alF'
alias la='ls -A'
alias l='ls -CF'

# Alias definitions.
# You may want to put all your additions into a separate file like
# ~/.bash_aliases, instead of adding them here directly.
# See /usr/share/doc/bash-doc/examples in the bash-doc package.

if [ -f ~/.bash_aliases ]; then
    . ~/.bash_aliases
fi

# enable programmable completion features (you don't need to enable
# this, if it's already enabled in /etc/bash.bashrc and /etc/profile
# sources /etc/bash.bashrc).
#if [ -f /etc/bash_completion ] && ! shopt -oq posix; then
#    . /etc/bash_completion
#fi

export PATH=/usr/local/cuda-9.0/bin${PATH:+:${PATH}}
export LD_LIBRARY_PATH=/home/ivcl/anaconda2/lib
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/home/ivcl/caffe/distribute/lib
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/home/ivcl/caffe/lib
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/lib
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/cuda-9.0/lib64
export PYTHONPATH=/home/ivcl/caffe/python

# >>> conda initialize >>>
# !! Contents within this block are managed by 'conda init' !!
__conda_setup="$('/home/ivcl/anaconda2/bin/conda' 'shell.bash' 'hook' 2> /dev/null)"
if [ $? -eq 0 ]; then
    eval "$__conda_setup"
else
    if [ -f "/home/ivcl/anaconda2/etc/profile.d/conda.sh" ]; then
        . "/home/ivcl/anaconda2/etc/profile.d/conda.sh"
    else
        export PATH="/home/ivcl/anaconda2/bin:$PATH"
    fi
fi
unset __conda_setup
# <<< conda initialize <<<