리뷰 Google Cloud 기초: Cloud Storage 및 Cloud SQL 시작하기개

Madhav M. · 24일 전에 리뷰됨

Dev T. · 24일 전에 리뷰됨

The startup script for the bloghost VM fails on first boot. When the script runs, the OS’s own apt-get process (likely unattended upgrades) is still holding the dpkg lock (/var/lib/dpkg/lock-frontend), so apt-get install fails. Apache is never installed, and the script exits with status 5 (“Unit apache2.service not found”). The VM appears healthy, but the web server is missing, and I had to SSH in and re-run the startup script manually to continue the lab. Suggested fix: make apt wait for the lock instead of failing, e.g. apt-get -o DPkg::Lock::Timeout=300 install -y apache2 php php-mysql, and add set -e so failures are visible. It would also help to mention in the instructions how to verify the startup script ran successfully (checking the serial port output for “exit status 0”).

Cesar C. · 24일 전에 리뷰됨

Craig H. · 24일 전에 리뷰됨

Michael Owen M. · 24일 전에 리뷰됨

A3-B3-63_MayankNarnaware G. · 24일 전에 리뷰됨

Zishan Ahmed S. · 24일 전에 리뷰됨

Manuel D. · 24일 전에 리뷰됨

Varadesh K. · 24일 전에 리뷰됨

Matt B. · 24일 전에 리뷰됨

the startup script didnt work, had to manually create the Apache server

João V. · 24일 전에 리뷰됨

Jonathan X. · 24일 전에 리뷰됨

Jauffrey F. · 24일 전에 리뷰됨

Olive M. · 24일 전에 리뷰됨

Gabriel R. · 24일 전에 리뷰됨

Brendan M. · 24일 전에 리뷰됨

In this lab, the startup script in Task 2 failed because another apt-get process was holding the dpkg frontend lock. The script was correctly saved and executed, but Apache/PHP were not installed. As a result, Task 5 failed at “cd /var/www/html” because the directory did not exist; apache2.service was also missing. The startup log showed: “Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 1231 (apt-get)”. Rerunning the startup script later with “sudo google_metadata_script_runner startup” resolved the issue, and I completed the lab. The progress checks had already shown 100/100 before the web server was working. Please consider adding a wait/retry mechanism for package-manager locks and a check that Apache is installed and running, or a troubleshooting note for this situation.

Irina E. · 24일 전에 리뷰됨

Stephen R. · 24일 전에 리뷰됨

Zhong L. · 24일 전에 리뷰됨

Brian P. · 24일 전에 리뷰됨

Fathima R. · 24일 전에 리뷰됨

Eran Z. · 24일 전에 리뷰됨

15 October 2026

Ntombizakhona M. · 24일 전에 리뷰됨

James M. · 24일 전에 리뷰됨

Peter G. · 24일 전에 리뷰됨