Google Cloud Fundamentals : Premiers pas avec Cloud Storage et Cloud SQL avis

Madhav M. · Examiné il y a 24 jours

Dev T. · Examiné il y a 24 jours

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. · Examiné il y a 24 jours

Craig H. · Examiné il y a 24 jours

Michael Owen M. · Examiné il y a 24 jours

A3-B3-63_MayankNarnaware G. · Examiné il y a 24 jours

Zishan Ahmed S. · Examiné il y a 24 jours

Manuel D. · Examiné il y a 24 jours

Varadesh K. · Examiné il y a 24 jours

Matt B. · Examiné il y a 24 jours

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

João V. · Examiné il y a 24 jours

Jonathan X. · Examiné il y a 24 jours

Jauffrey F. · Examiné il y a 24 jours

Olive M. · Examiné il y a 24 jours

Gabriel R. · Examiné il y a 24 jours

Brendan M. · Examiné il y a 24 jours

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. · Examiné il y a 24 jours

Stephen R. · Examiné il y a 24 jours

Zhong L. · Examiné il y a 24 jours

Brian P. · Examiné il y a 24 jours

Fathima R. · Examiné il y a 24 jours

Eran Z. · Examiné il y a 24 jours

15 October 2026

Ntombizakhona M. · Examiné il y a 24 jours

James M. · Examiné il y a 24 jours

Peter G. · Examiné il y a 24 jours