Mengakses Konsol Google Cloud dan Cloud Shell Ulasan

Mateusz B. · Diulas 23 hari lalu

Shreya U. · Diulas 23 hari lalu

DEEKSHA MURALIDHARAN 2. · Diulas 23 hari lalu

PRANEETH G. · Diulas 23 hari lalu

Sahil c. · Diulas 23 hari lalu

JAYASHREE S. · Diulas 23 hari lalu

Maciej M. · Diulas 23 hari lalu

SHIV K. · Diulas 23 hari lalu

Emilia M. · Diulas 23 hari lalu

Sahil c. · Diulas 23 hari lalu

Helma Z. · Diulas 23 hari lalu

Sahak S. · Diulas 23 hari lalu

Martynas V. · Diulas 23 hari lalu

Nisha M. · Diulas 23 hari lalu

Aditi K. · Diulas 24 hari lalu

Mazen M. · Diulas 24 hari lalu

Sergei K. · Diulas 24 hari lalu

Miguel V. · Diulas 24 hari lalu

Alex A. · Diulas 24 hari lalu

Ankit G. · Diulas 24 hari lalu

YASH R. · Diulas 24 hari lalu

Lab issues identified during the session: APT Package Manager Lock: Upon starting the VM, the system immediately triggers background security updates that hold the dpkg lock for several minutes. This prevents the manual installation of nginx as instructed, causing "Could not get lock" errors. The lab should include a wait command or pre-install the service. Serial Port Metadata Conflict: The current UI for enabling the serial port via metadata is outdated. The Google Cloud Console now triggers a red validation error, forcing users to find the new "Remote Access" section instead of following the manual metadata entry shown in the instructions. Validation Lag: There is a significant delay (over 1-2 minutes) between completing the index.html task and the "Check my progress" button recognizing the change, even when curl localhost confirms the file is correctly served. Suggestion: Please update the instructions to account for background system updates and the new UI layout for serial port access.

Luis M. · Diulas 24 hari lalu

VIGNESH M. · Diulas 24 hari lalu

Udhaya N. · Diulas 24 hari lalu

MATAM PRAJWAL 2. · Diulas 24 hari lalu