docs: add Vagrant-based development environment setup guide #2416
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
There are 9 file changes on the PR? Can you rebase please, I think we need only one file change |
Signed-off-by: Mauricio Magnani <[email protected]>
msmagnanijr
force-pushed
the
add-vagrant-tips
branch
from
29d1c3f to
1001e5d
Compare
|
Closing in favor of #2417 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What is this PR doing:
This PR adds documentation for setting up a development environment using Vagrant. Since Fedora uses Podman by default, this guide provides instructions on configuring a Vagrant-based VM to run Docker, ensuring a consistent development environment while avoiding conflicts with the host system's package management.
Issue: No-Issue
Reviewers must know:
It includes instructions for setting up and running a Vagrant VM, installing dependencies, and ensuring Docker is properly configured.
No code changes are introduced, only documentation.