찾으시는 취미가 있나요?

클래스 스토리1493개의 글

인기순최신순
크리에이터가 고정함
classmate
2/6/2021
Following the last lecture, those who are conducting this lecture will have to get-started at 80 ports in the docker, so I think you should lower it. >> sudo docker ps >> docker stop [container id]
38
원본 보기
Foo
크리에이터
2/6/2021
Thank you for pointing out the good points. :)
원본 보기
크리에이터가 고정함
Classmate631619n
2/8/2021
May I know why the authorized_keys file will be deleted after entering the public key in authorized_keys?
27
원본 보기
Classmate502257m
2/8/2021
I'm curious about this, too.
원본 보기
Foo
크리에이터
2/8/2021
Hello! This issue is due to the GCP managing its own SSH key file, authrized_keys. Because we created the instance, it's likely to be entirely under our control. These instances are all controlled by GCP functions. The authorized_keys file is one of them, and to fully add it to the list of public keys here, you'll be able to: You should go to Metadata - SSH Key - Modify from the left menu and add the public key as shown in the lecture note. This adds its public key to all instances, eliminating the need to add authorized_keys each time.
원본 보기
Foo
크리에이터
2/8/2021
The information will be available in the next lecture, 3-29:43, so please refer to it!
원본 보기
크리에이터가 고정함
classmate
4/19/2021
If there is an error in the excuser process among M1 Mac users. Erase the Docker container image. docker buildx create --name m1_builder docker buildx use m1_builder Run until docker buildx inspection --bootstrap. docker buildx build --platform linux/amd64,linux/arm64,linux/arm/v7 -t 레파지토리이름:태그 --push . If you do it, you can push it to the repertoire. If there is an error here, you can just erase the arm/v7 part and rebuild it. If you do it with this, it will work normally. I posted it separately just in case there are people who can't find related questions right away. Thank you for the good lecture.
17
원본 보기
Foo
크리에이터
4/19/2021
Thank you, twosom. :) If other M1 users have any problems while practicing, please refer to this information!
원본 보기
classmate
7/22/2021
docker buildx build --platform linux/amd64,linux/arm64,linux/arm/v7 -t huiwater/spring-boot-cpu-bound --push error: "docker buildx build" requires exactly 1 argument. See 'docker buildx build --help'. Usage: docker buildx build [OPTIONS] PATH | URL | - Start a build
Foo
크리에이터
7/22/2021
@soo Soo, I think you took out the last one. Please check.
원본 보기
크리에이터가 고정함
Foo
크리에이터
5/23/2021
Scripts from 3:28 Core Concepts have been moved elsewhere. You have to go to the next link. https://artillery.io/docs/guides/getting-started/writing-your-first-test.html#Load-Phases
15
원본 보기
로그인하면
더 많은 실제 후기를 만날 수 있어요!
클래스101은 모든 사람이 사랑하는 일을 하며
살 수 있도록 세상을 바꾸고자 합니다.
크리에이터
정규 클래스 지원하기
도움말
고객센터
오전 10시 ~ 오후 6시 (주말, 공휴일 제외)
주식회사 클래스101 | 대표 공대선 | 서울특별시 강남구 테헤란로 415, 4층(삼성동, 엘7강남타워) | ask@101.inc | 전화번호: 1800-2109 | 클라우드 호스팅: Amazon Web Services Korea LLC | 사업자등록번호 : 457-81-00277 | 통신판매업신고 : 2022-서울강남-02525 | 클래스101은 통신판매중개자로서 중개하는 거래에 대하여 책임을 부담하지 않습니다.