Fails failed to StartContainer: API error (500): With no Install Profile selected

[bsnodgrass]

Describe the bug

On Open Dev Env in Drupalpod extension... Environment starts to build with error in terminal.

Failed to start drupalpod: failed to StartContainer: API error (500): OCI runtime create failed: container_linux.go:367: starting container process caused: process_linux.go:495: container init caused: rootfs_linux.go:60: mounting "proc" to rootfs at "/proc" caused: operation not permitted: unknown

To Reproduce

On a Drupal.org issue, proceed to the Drupalpod extension. Fill out Drupalpod selections and DO NOT include a selection for Install profile.

Using the following example worked

Version and configuration information (please complete the following information)

• Issue page https://www.drupal.org/project/login_onlyemail/issues/3147964
• Issue branch See Image
• Drupal core version See Image
• Project type
• Core
• [ X] Module
• Theme

Additional context

Having an Install Profile as default (Standard?) would solve this problem.

Can the text above the drop downs be changed to "Select from the options below (Required):"

A future "nice to have" would be configuration to select a preferred install profile.

[shaal]

Thank you @bsnodgrass for submitting this issue.
The problem comes from upstream - there's currently an issue with the Gitpod service, docker and docker-compose commands are failing - gitpod-io/gitpod#5171

[shaal]

To clarify, this is not related to the choices you made using the DrupalPod extension. Hopefully Gitpod will resolve it quickly :)

[shaal]

This issue should be resolved now.

[bsnodgrass]

confirmed... closing issue