Hyper-v usage of dynamic memory - yank from the grave

Archive Feature Requests
1

I may be naïve (since I’m new to the community) but it would be nice to have a location to have feature requests that can persists in spirit, even though denied/closed. An example that I personally care about is having Docker dynamically allocate memory resources in Hyper-v. For those who follow the topics, others have brought it up:

Hyper-v usage of dynamic memory

and its been closed.

Well as a user, having a location for liked minded individuals to have their requests backlogged would be feel great. Going back to the above example, it’s understandable why the issue is closed, but what if there is someone who wants to take on the challenge and solves it? There would be a group of very thankful people waiting for that solution. So back to the main topic of the rant, is there a location in this community to persist denied requests? I’m hoping that if the developers see a count rising for a feature, it may get some love one day.

What do you guys think?

2

Until I read the whole post I wasn’t sure what you meant by

as you just posted in the “Fatrure requests” category and we don’t delete real feature requests. Then I realized you shared a feature request in the docker/for-win GitHub repository and you are probably looking for the roadmap:

I guess these can be closed too, but if I filter to the “wontfix” label, there is no result.

Who do you think could solve it? :slight_smile: Docker Desktop is not open source, so if Docker don’t want to solve it, who can?

1 Like