Skip to content

[Scenario] Moving projects to Docker #2702

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
BillWagner opened this issue Jul 21, 2017 · 4 comments
Closed

[Scenario] Moving projects to Docker #2702

BillWagner opened this issue Jul 21, 2017 · 4 comments
Labels
dotnet-docker/subsvc won't fix Issues that were closed as part of automated backlog grooming

Comments

@BillWagner
Copy link
Member

This scenario will explain to developers how to migrate their existing projects to Docker containers.

@mairaw mairaw modified the milestone: 2017 - Quarter 3 Jul 31, 2017
@mairaw mairaw modified the milestones: 2017 - Quarter 4, 2017 - Quarter 3 Sep 5, 2017
@JRAlexander JRAlexander modified the milestones: 2017 - Quarter 4, 2018 - Quarter 1 Dec 18, 2017
@JRAlexander
Copy link
Contributor

@BillWagner
Copy link
Member Author

I think all the information is in the doc you reference. However, I don't think the information is structured to make it clear to a reader that it's got the information they seek. I'd recommend adding a new introduction that introduces the scenario, and uses the phrase "lift and shift" to explain that the reader will learn how to take an existing application, migrate to docker and run it in a container. Along the way, you'll learn important concepts about working with docker.

Thoughts @JRAlexander ?

@BillWagner BillWagner added the P1 label Mar 6, 2018
@JRAlexander
Copy link
Contributor

I agree. I think we could create a new doc that specifically addresses that scenario, but looks very similar to the current one.

@BillWagner BillWagner removed this from the March 2020 milestone Mar 31, 2020
@dotnet-bot
Copy link
Contributor

This issue has been closed as part of the issue backlog grooming process outlined in #22351.

That automated process may have closed some issues that should be addressed. If you think this is one of them, reopen it with a comment explaining why. Tag the @dotnet/docs team for visibility.

@dotnet-bot dotnet-bot added the won't fix Issues that were closed as part of automated backlog grooming label Jan 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dotnet-docker/subsvc won't fix Issues that were closed as part of automated backlog grooming
Projects
None yet
Development

No branches or pull requests

6 participants