Opiniones sobre Aspectos básicos de Google Cloud: introducción a Cloud Storage y Cloud SQL

Madhav M. · Se revisó hace 24 días

Dev T. · Se revisó hace 24 días

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. · Se revisó hace 24 días

Craig H. · Se revisó hace 24 días

Michael Owen M. · Se revisó hace 24 días

A3-B3-63_MayankNarnaware G. · Se revisó hace 24 días

Zishan Ahmed S. · Se revisó hace 24 días

Manuel D. · Se revisó hace 24 días

Varadesh K. · Se revisó hace 24 días

Matt B. · Se revisó hace 24 días

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

João V. · Se revisó hace 24 días

Jonathan X. · Se revisó hace 24 días

Jauffrey F. · Se revisó hace 24 días

Olive M. · Se revisó hace 24 días

Gabriel R. · Se revisó hace 24 días

Brendan M. · Se revisó hace 24 días

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. · Se revisó hace 24 días

Stephen R. · Se revisó hace 24 días

Zhong L. · Se revisó hace 24 días

Brian P. · Se revisó hace 24 días

Fathima R. · Se revisó hace 24 días

Eran Z. · Se revisó hace 24 días

15 October 2026

Ntombizakhona M. · Se revisó hace 24 días

James M. · Se revisó hace 24 días

Peter G. · Se revisó hace 24 días