henrybear327 commented on PR #10075:
URL: https://github.com/apache/ozone/pull/10075#issuecomment-4239447337

   > Thanks @henrybear327 for the patch. Please link to relevant docs that 
describe devcontainers.
   > 
   > > ## How was this patch tested?
   > > 
   > > * Locally on M-series Mac
   > > * Creating a new Github Codespace
   > 
   > Can you please provide steps?
   
   Sorry for being too brief on this matter. 
   
   The official website is https://containers.dev/ - "A development container 
(or dev container for short) allows you to use a container as a full-featured 
development environment. It can be used to run an application, to separate 
tools, libraries, or runtimes needed for working with a codebase, and to aid in 
continuous integration and testing."
   
   The main benefits are that developers can quickly spin up a Github Codespace 
and start working on the project, or, locally, a devcontainer, such that all 
toolchains required for developments are setup already.
   
   It's also used in a lot of [Apache 
projects](https://github.com/search?q=org%3Aapache+path%3A.devcontainer%2Fdevcontainer.json&type=code).
 
   
   ---
   
   Locally, I followed the [devcontainer CLI 
guide](https://code.visualstudio.com/docs/devcontainers/devcontainer-cli#_running-the-cli)
 here to install and spin up a devcontainer instance. As docker-in-docker in 
enabled, I followed the README and ran `cd 
hadoop-ozone/dist/target/ozone-*/compose/ozone; docker compose up -d --scale 
datanode=3` to see if I can spin up a cluster.
   
   On github, I created a codespace against this branch, as shown in the 
following image:
   <img width="1269" height="464" alt="Screenshot 2026-04-13 at 10 34 06 PM" 
src="https://github.com/user-attachments/assets/f267e60f-3768-44ed-a169-94bbae25936d";
 />
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to