Drupal-GitPod VS workspace-images

This post continues a mini-series in which I describe how I created a generic Drupal-friendly container working with GitPod. The code is available in my GitHub.

The entire project is available in my GitHub.

In this mini-series I describe how I created a generic Drupal-friendly container working with GitPod. It is available in my GitHub. Note that since this is some code I may continue using over time, the code there may change beyond what is covered in this article.

This solution starts from the GitPod-provided MySQL image. That does not give everything you need for a functioning Drupal site, but it does meet the basics of a LAMP stack.

You might need to replicate some steps from https://github.com/gitpod-io/workspace-images/blob/main/base/Dockerfile inside your dockerfile.

It occurred because go install was run by root in the Dockerfile. So running sudo will solve it, but the image doesn't have the command. By the way, it won't occur in the official image because it sets the USER properly.

By default, Gitpod uses the gitpod/workspace-full image which includes a lot of tools which weren't needed for Telescope. Since Telescope only really requires Docker, Node and pnpm, creating a custom Dockerfile to have a smaller image for the gitpod workspace using gitpod/workspace-base would be much better than using the default one.

Both Gitpod and Github Codespaces have config files based on Docker that configures your whole env. On Gitpod their config system uses a .gitpod.yml file which stores your workspace config info and a .gitpod.Dockerfile file which sets up a docker image that you can use to run your workspace. By default, Gitpod uses a standard docker image as the foundation for workspaces, the standard image has most of the default tools and programs devs require, plus you can also build on top of it to add small additions to it.