Problem with Lets Encrypt Certificates and the Git client about gitpod-laravel-starter

[strausmann]

Ok, have to correct myself a bit. With the FROM gitpod/workspace-mysql:legacy-dazzle-v1 only the 1.4.0 image works again. With the 1.5.0 image I still have problems with the Git client and my own GitLab instance.

[apolopena]

Ok we can fix this by pinning the Gitpod workspace-mysql image version to a specific date:
gitpod-io/workspace-images#595 (comment)

Not my favorite solution but perhaps we can create and maintain our own underlying image in the future.

[apolopena]

There are alot of moving parts on this one from me to even to be able to test it out. Not super sure where to start.

[apolopena]

Something along the lines of this?
https://docs.gitlab.com/ee/integration/gitpod.html

[apolopena]

Did you register your self hosted gitlab instance with Gitpod?
https://www.gitpod.io/docs/gitlab-integration#registering-a-self-hosted-gitlab-installation

[strausmann]

I've been using GitPod with my GitLab self-hosted instance since GitPod first supported it.

So I don't see any problem with the GitPod integration at the moment.
I think GitPod has changed something in the base image again and that's why the build doesn't work anymore.

However, I just created a new repository and then used the "gitpod/workspace-mysql" image as a base. Here there are no problems when pushing to the gitlab instance from me.

[strausmann]

So, I tried something again. Changed the base image to this day.

FROM gitpod/workspace-mysql:legacy-dazzle-v1

With this, both the build of the workspace and my git push works again.

[apolopena]

workspace-mysql:2022-02-04-10-54-10 did not work for me

[apolopena]

It looks like there is no version of workspace-mysql where nginx, PHP, and Apache are retained but ca certificates work. Since these are the only two tags we have to work with:
(contains nginx, PHP and apache but has buggy ca certificates)
https://hub.docker.com/layers/gitpod/workspace-mysql/legacy-dazzle-v1/images/sha256-d75a730768eba3eacf854e4dd671967a2c07d81cee44ec51e85c1265ec1b2baf?context=explore
and
(does not contain nginx, PHP and apache but ca certificates are fixed?)
https://hub.docker.com/layers/gitpod/workspace-mysql/2022-02-04-10-54-10/images/sha256-89974ad5bffbd7f1a5f68070f81e414d9a4d1be923d0b606177711462c83c1df?context=explore

Please advise how I can workaround this.

Its looking like I will have to use workspace-full and then integrate mysql on my own? I would really rather not do that to hotfix this breaking change in a bunch of my projects, including portfolio pieces.

[apolopena]

@strausmann
I am hoping for a suggested workaround (from Gitpod) that actually works.

Otherwise I will have to integrate mysql in this projects gitpod.Dockerfile and build the project on workspace-full:some pinned-date.

Thoughts?

[apolopena]

@strausmann
Gitpod fixed this issue. I reverted the hotfix. Let me know if you still see this issue in v1.5.0
Thanks!

[apolopena]

@strausmann
I will assume this has been fixed since it was a regression issue that was addressed by Gitpod.
Feel free to re-open this after v.16 is released if you continue to experience the issue.

[strausmann]

@apolopena
Sorry. forgot to give feedback. :-)
With the new base image from GitPod my LE problem is also fixed.