リモート起動スクリプトを使用した Compute インスタンスのデプロイ: チャレンジラボ のレビュー

Paccaud Marc · 2ヶ月前にレビュー済み

Mai Dion · 2ヶ月前にレビュー済み

labasbas Michelle · 2ヶ月前にレビュー済み

Subbiah Sankara Subramanian · 2ヶ月前にレビュー済み

chokshi pintu · 2ヶ月前にレビュー済み

RAMESH Preethi · 2ヶ月前にレビュー済み

Moskovitz Tal · 2ヶ月前にレビュー済み

Saqib Muhammad Naveed · 2ヶ月前にレビュー済み

Firmansyach Windu · 2ヶ月前にレビュー済み

BEFOLO AKOUMOU Landry Freidy · 2ヶ月前にレビュー済み

Vadlamudi Tejaswini · 2ヶ月前にレビュー済み

Mallampati Sneha · 2ヶ月前にレビュー済み

Mohdisa Aidil · 2ヶ月前にレビュー済み

Coliñir Nicanor · 2ヶ月前にレビュー済み

Naniwadekar Amey · 2ヶ月前にレビュー済み

abdelrehim amgad refaat amin · 2ヶ月前にレビュー済み

Zimny Tomasz · 2ヶ月前にレビュー済み

I've identified and fixed the issues preventing your VM from serving web content. What went wrong: 1. Windows Line Endings: Your install-web.sh file had Windows-style line endings (\r\n). When Linux tried to run the script, it saw the command as apt-get update\r, which is an invalid operation. 2. Leading Space: There was a space at the very beginning of your script ( #!/bin/bash), which can sometimes interfere with how the shell interprets the file. 3. Apt Lock: On the first boot, your script failed because another system process (likely the automatic agent installation) was already using the package manager (apt-get). What I did: 1. Cleaned the Script: I removed the Windows carriage returns and the leading space from install-web.sh. 2. Updated the Bucket: I uploaded the corrected script back to your GCS bucket. 3. Restarted the VM: I reset the web2 instance to force it to run the startup script again. Verification: I verified that the VM is now correctly serving the default Apache page: 1 HTTP/1.1 200 OK 2 Server: Apache/2.4.67 (Debian) You should now be able to go back to the lab console and successfully validate the "test that the vm is serving web content" step!

Moritz Lennart Joshua · 2ヶ月前にレビュー済み

K Ganapathi · 2ヶ月前にレビュー済み

kanyo Abderrahmen · 2ヶ月前にレビュー済み

A MW · 2ヶ月前にレビュー済み

Temirov Emil · 2ヶ月前にレビュー済み

Singh Naveen · 2ヶ月前にレビュー済み

Harsh s Patel · 2ヶ月前にレビュー済み

Cook Tony · 2ヶ月前にレビュー済み