8000 [Project] DevContainer configuration by cheina97 · Pull Request #3062 · liqotech/liqo · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

[Project] DevContainer configuration #3062

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 2, 2025
Merged

[Project] DevContainer configuration #3062

merged 1 commit into from
Jul 2, 2025

Conversation

cheina97
Copy link
Member
@cheina97 cheina97 commented Jun 28, 2025

Description

This PR adds a .devcontainer/devcontainer.json file to provide a reproducible, feature-rich development environment for the project. The configuration is based on Debian GNU/Linux 12 (bookworm) and is optimized for Go, and Kubernetes workflows.

Main Features

  • Go Development: Includes Go and common Go utilities pre-installed and available on the PATH, along with the Go language extension for enhanced Go development.
  • Up-to-date Git: Ships with an up-to-date version of Git, built from source if needed, and available on the PATH.
  • Docker CLI: The Docker CLI (docker) and Docker Compose v2 are pre-installed, allowing container management using the host's Docker daemon.
  • GitHub CLI: The latest GitHub CLI (gh) is installed and available on the PATH.
  • Kubernetes in Docker (KinD): Includes KinD for running local Kubernetes clusters, supporting Kubernetes-native development and testing.
  • Enhanced Shell Experience: Zsh is set as the default shell, with Oh My Zsh, Powerlevel10k theme, and a curated set of plugins (e.g., autosuggestions, syntax highlighting, kubectl, docker, git, golang, helm).
  • Host Home Directory Mount: Mounts the host's home directory as read-only at /mnt/hosthome for easy access to configuration files and credentials.
  • Automatic Powerlevel10k Setup: If a .p10k.zsh config is found in the host's home, it is copied and sourced automatically in the container.
  • Automatic Package Upgrades: System packages are upgraded on container creation, including support for non-free packages.
  • Network Capabilities: With this devcontainer setup is possible to perform networking actions, like creating linux network namespaces and new network interfaces.

Behaviours

  • On container start, the Powerlevel10k theme is installed and configured if a .p10k.zsh file is present.
  • Zsh plugins and Oh My Zsh plugins are installed for the vscode user.

@adamjensenbot
Copy link
Collaborator

Hi @cheina97. Thanks for your PR!

I am @adamjensenbot.
You can interact with me issuing a slash command in the first line of a comment.
Currently, I understand the following commands:

  • /rebase: Rebase this PR onto the master branch (You can add the option test=true to launch the tests
    when the rebase operation is completed)
  • /merge: Merge this PR into the master branch
  • /build Build Liqo components
  • /test Launch the E2E and Unit tests
  • /hold, /unhold Add/remove the hold label to prevent merging with /merge

Make sure this PR appears in the liqo changelog, adding one of the following labels:

  • feat: 🚀 New Feature
  • fix: 🐛 Bug Fix
  • refactor: 🧹 Code Refactoring
  • docs: 📝 Documentation
  • style: 💄 Code Style
  • perf: 🐎 Performance Improvement
  • test: ✅ Tests
  • chore: 🚚 Dependencies Management
  • build: 📦 Builds Management
  • ci: 👷 CI/CD
  • revert: ⏪ Reverts Previous Changes

@cheina97 cheina97 marked this pull request as draft June 28, 2025 13:05
@cheina97 cheina97 marked this pull request as ready for review June 28, 2025 18:53
@cheina97 cheina97 merged commit 1b9dd7d into master Jul 2, 2025
10 checks passed
@cheina97 cheina97 deleted the frc/devcontainer branch July 2, 2025 11:36
@frisso
Copy link
Member
frisso commented Jul 2, 2025

@cheina97 I would suggest to take the description of this PR, transform it into a README, and add to the .devcontainer folder.
If you like, I can take this task for myself.
Overall, good job!

@cheina97
Copy link
Member Author
cheina97 commented Jul 2, 2025

@cheina97 I would suggest to take the description of this PR, transform it into a README, and add to the .devcontainer folder.
If you like, I can take this task for myself.
Overall, good job!

I agree, I can do it. Nothing too demanding

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants
0