Build and Run Discussion #6072
Replies: 1 comment
-
Hi @slominskir, Our main target platform is RHEL. So our development/testing workflows are heavily skewed towards RHEL on BM/VM. That said, I see how having a devcontainer can make it easier for others to contribute. So feel free to submit your PR for a review. I think it'd be pretty cool to make it work on WSL or Mac. |
Beta Was this translation helpful? Give feedback.
-
Hi,
Would be nice if the build and run instructions were easier and more portable. I'm usually on Windows (Ubuntu WSL), Mac, or RHEL. The build instructions are tailored for Fedora or CentOS. Ideally the dev environment just runs in a container. This is already happening with GitHub Action, but it still requires a little work to adapt to run on a local container runtime during development. For one there are multiple containers, one for compile, then multiple for testing. Would be nice to consolidate to a single dev container that is not tied to GitHub Action (I guess there might be a run GitHub action locally plugin?).
There is also "devcontainer" spec, but that might be unnecessary and too tightly tied to GitHub/Microsoft/VisualStudioCode.
I am actually trying to build/test changes to dscontainer. I've extended the ci compile container and added some dscontainer runtime pieces in a dev-container-discussion branch. Trying to get a simple process, and this is what I have so far:
Currently just bind mounting the source into the container. Remote dev via ports requires more tooling, but might avoid filesystem permission issues.
Build references:
https://www.port389.org/docs/389ds/development/building.html
Container references:
Thoughts?
Regards,
Ryan
Beta Was this translation helpful? Give feedback.
All reactions