Local time: 금 2023-04-14 16:14:51 UTC Universal time: 금 2023-04-14 16:14:51 UTC RTC time: 금 2023-04-14 16:14:51 Time zone: Etc/UTC (UTC, +0000) System clock synchronized: yes NTP service: active RTC in local TZ: no
정확한 TimeZone 명칭을 확인해보고,
$ sudo timedatectl list-timezones | grep Seoul
Asia/Seoul
설정해주면 된다.
$ sudo timedatectl set-timezone Asia/Seoul
$ sudo timedatectl
Local time: 토 2023-04-15 01:16:05 KST Universal time: 금 2023-04-14 16:16:05 UTC RTC time: 금 2023-04-14 16:16:05 Time zone: Asia/Seoul (KST, +0900) System clock synchronized: yes NTP service: active RTC in local TZ: no
심지어 "System clock synchronized: yes"라고 되어있는 것을 보면 시간 동기화 설정도 이미 되어있다!
개인적인 취향에 따른 설정도 추가적으로 해보자.
vi를 싫어하고 nano를 사용하기에 nano 기본 설정값을 넣어보겠다.
$ nano ~/.nanorc
tab을 공백 4칸으로 설정하는 것이다.
set tabsize 4 set tabstospaces
root 권한으로 사용하는 경우, 특히 sudo 사용할 때를 위해서 추가적으로... (내용은 동일)
master$ kubectl cluster-info Kubernetes control plane is running at https://127.0.0.1:6443
To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.
master$ kubectl get nodes NAME STATUS ROLES AGE VERSION node1 Ready control-plane,master 14m v1.20.7 node2 NotReady <none> 13m v1.20.7 node3 NotReady <none> 13m v1.20.7
- 이제 준비된 VirtualBox Image를 Vagrant Image로 convert 해보자.
- VirtualBox Guest 파일들이 저장된 위치를 찾아서 이동
> dir
total 14473272
drwxr-xr-x 1 whatw 197609 0 7월 4 18:30 Logs/
drwxr-xr-x 1 whatw 197609 0 7월 4 18:23 Snapshots/
-rw-r--r-- 1 whatw 197609 20613 7월 4 18:30 'Ubuntu 20.04 Server Worker1.vbox'
-rw-r--r-- 1 whatw 197609 20642 7월 4 18:23 'Ubuntu 20.04 Server Worker1.vbox-prev'
-rw-r--r-- 1 whatw 197609 14820573184 5월 5 16:49 'Ubuntu Server 20.vdi'
- `package` 명령어를 이용해서 convert 하면 된다.
- 아래 타이핑한 내역을 잘 살펴보기 바란다 (.vbox 사용하지 않기와 같은...^^)
> vagrant package --base "Ubuntu 20.04 Server Worker1" --out "ubuntu2004server.box"
==> Ubuntu 20.04 Server Worker1: Attempting graceful shutdown of VM...
Ubuntu 20.04 Server Worker1: Guest communication could not be established! This is usually because
Ubuntu 20.04 Server Worker1: SSH is not running, the authentication information was changed,
Ubuntu 20.04 Server Worker1: or some other networking issue. Vagrant will force halt, if
Ubuntu 20.04 Server Worker1: capable.
==> Ubuntu 20.04 Server Worker1: Forcing shutdown of VM...
==> Ubuntu 20.04 Server Worker1: Exporting VM...
==> Ubuntu 20.04 Server Worker1: Compressing package to: C:/Users/whatw/VirtualBox VMs/Ubuntu 20.04 Server Worker1/ubuntu2004server.box
06. add Box
- 위에서 만든 Box를 등록하는 과정이다
> vagrant box add "ubuntu2004server" "C:\Users\whatw\ubuntu2004server.box"
==> box: Box file was not detected as metadata. Adding it directly...
==> box: Adding box 'ubuntu2004server' (v0) for provider:
box: Unpacking necessary files from: file:///C:/Users/whatw/ubuntu2004server.box
box:
==> box: Successfully added box 'ubuntu2004server' (v0) for 'virtualbox'!
07. SHASUM
- 뒤에 사용될 것을 미리 확인해놓자
- 파일 이름 뒤의 `SHA256`을 꼭 써줘야 한다!!!
> certutil -hashfile .\ubuntu2004server.box sha256
SHA1의 .\ubuntu2004server.box 해시:
7e6b73addaaea6c430c54dc16fd968ba740c7272e68807e0cf57f6fa5e28c499
CertUtil: -hashfile 명령이 성공적으로 완료되었습니다.
08. Vagrant Cloud 준비
- `03. Vagrant Hub ?`에서 회원가입을 했다면 아래와 같은 화면을 확인할 수 있다.
- `Create a new Vagrant Box` 클릭하고 계속 진행해보자.
- 버전은... 링크로 있는 `RubyGems versioning`을 한 번 확인해보기 바란다.
- 제대로 사용하도록 하려면 사실 `1.0.0`으로 해주는 것이...
- 앞에서 미리 확인한 SHA Checksum 값을 넣어주면 된다. (위의 이미지에 있는 Checksum 값은 틀렸다 ^^)
정신없는 업무로 한동안 집에서 컴퓨터를 만지지 못하다가,
간만에 집에서 뭔가 해보려 VirtualBox를 실행했는데... 새로운 버전이 나왔단다.
VirtualBox 4.3.6 (released 2013-12-18)
This is a maintenance release. The following items were fixed and/or added:
VMM: fixed a Guru Meditation VINF_EM_TRIPLE_FAULT caused by VMCB caching with nested paging on certain AMD CPUs (bug #12451) VMM: fixed a Guru Meditation VERR_VMX_UNEXPECTED_INTERRUPTION_EXIT_TYPE while intercepting debug exceptions (VT-x only; bug #12410) VMM: fixed a Guru Meditation VERR_SVM_UNEXPECTED_EXIT while intercepting debug register accesses (AMD-V only; bug #12481) VMM: fixed a VERR_SSM_STRUCTURE_MAGIC error when trying to load a saved state made with VBox 4.3.4 when VT-x/AMD-V is disabled. Unfortunately, VBox 4.3.4 produced broken saved states for this configuration so you have to discard these states (bug #12414) VMM: added a few more MSRs to the whitelist required by certain guests (bug #12245) GUI: fixed deleting of inaccessible VMs (4.3 regression, bug #12205) GUI: fixed warnings in VM settings / number of guest processors (bug #12480) Main: don't automatically enable 64-bit guests on 64-bit hosts if VT-x/AMD-V is not available (bug #12424) Main: always expose the DMI memory information to Windows 2012 guests (bug #12017) Main: fixed occasional crashes on guest display resolution change (bug #7063) Main: fixed reporting back temporary name when calling IGuestSession::DirectoryCreateTemp() (bug #12498) API: fix for a hang when launching a GUI VM through the API, which crashes due to GUI unavailability Storage: fix for BLKCACHE_IOERR runtime errors under rare circumstances (bug #11030) Network: allow to start more than 5 PCNet instances (bug #12426) E1000: if the cable was disconnected before the guest initialized the device, the link status was not properly set to 'down' after the initialization completed despite the fact that there was no connection 3D support: fixed offset of guest 3D image elements (Mac OS X Retina hosts only; bug #11021) Solaris hosts: fixed accessing the host driver from non-global zones (4.3 regression, bug #12271)
뭔가 어려운 내용들이 개선이 된 것 같은데, 피부에 와닿는 부분은 잘 모르겠다 ^^
그냥 계속 되는 개선이 고마울 뿐....