gitpod-samples/awesome-gitpod

[submission]: Custom Docker image with different Linux distros

sprucecellodev125 opened this issue · 6 comments

sprucecellodev125 commented

Project link

https://sprucecellodev125.github.io/custom-gitpod-image/

Kind

Tutorial

What is this?

So in this tutorial you'll create Gitpod workspace with your favourite Linux distributions from Debian to Arch with most development tools that's present in gitpod/workspace-full

Additional context/comments

Well, however there's still a problem:

  • SSH might not work as expected, means desktop version of VSCode, and IDEs can't connect to the workspace
  • Lack of version manager (ex. nvm)

However the rest (and also Docker) is work as expected and even have custom bash prompt

Code of Conduct

  • I agree to follow this project's Code of Conduct
Siddhant-K-code commented

👋🏽 @sprucecellodev125

Thanks for the contribution. Do you know how we can proceed from here?

In past, we did something like this #16 (comment). Do You Want us to import your repository to gitpod-samples org? Then, you & we maintain the repository.

sprucecellodev125 commented

👋🏽 @sprucecellodev125

Thanks for the contribution. Do you know how we can proceed from here?

In past, we did something like this #16 (comment). Do You Want us to import your repository to gitpod-samples org? Then, you & we maintain the repository.

yes

  • 👍1
Siddhant-K-code commented

@sprucecellodev125 I've imported the repo. (gitpod-samples/custom-linux-distro-gitpod) here, feel free to send out the updates. Once again, Thanks a lot for the contribution ✨

Siddhant-K-code commented

@sprucecellodev125, I've updated the readme details, but it still lacks the GitHub image registry as it requires some secrets (tail scale, PAT, etc.) to build the image from this workflow. I will, later on, add these secrets & build out the GitHub container registry image.

axonasif commented

I'm not familiar with such a GitHub workflow. But I wonder why do we need tailscale in there?

  • 👀1
sprucecellodev125 commented

I'm not familiar with such a GitHub workflow. But I wonder why do we need tailscale in there?

I used tailscale instead of ngrok for SSH access to debug the build failure and I still made some typo in the dockerfile before 😆

@sprucecellodev125, I've updated the readme details, but it still lacks the GitHub image registry as it requires some secrets (tail scale, PAT, etc.) to build the image from this workflow. I will, later on, add these secrets & build out the GitHub container registry image.

PAT = Personal access token to push image to container registry
tailscale = Ephemeral tailscale auth key (used for SSH debugging)

Unless if we can use this org github container registry I removed those workflow

  • 👍2