linka-cloud / linka-cloud/d2vm
d2vm discover and proposal
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 373
- Forks
- 61
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
Thanks for the great work ! Your software is a really good idea !
It's exactly the tool i needed for my projects.
I've successfully convert a postgres docker file into a qcow2 vm image.
d2vm convert postgres:16-alpine -o postgres.qcow2 -p laurent
But as pointed by your README.md, the entrypoint, CMD and ENV are not yet convert into the image. So for now, some manual work are still needed to use the vm created by d2vm.
I've thought also that a docker-compose.yml could be also be handled by your tool.
It could allow to create seperate vm with one or more services from the docker-compose.yml.
Have you planned to add this stuff or do you know an existing tool more advance than yours ?
Would you need some help on this project ? I don't know if i will have time but i could perhaps motivate some friends to help ?
Best Regards,
++
Laurent
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with README.md and the existing d2vm convert flow described in the issue. Determine the scope for preserving Dockerfile ENTRYPOINT, CMD, and ENV values and for accepting docker-compose.yml services; done should be defined by concrete conversion behavior and coverage for the requested cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose, dockerfile, go
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100