Skip to content

Conversation

@mattwelke
Copy link
Contributor

@mattwelke mattwelke commented Aug 24, 2019

Proposed Changes

Tested by building the image before and after this Dockerfile change and ensuring they both worked the same way (responded to requests on a port specified by PORT env var).

@googlebot googlebot added the cla: yes Indicates the PR's author has signed the CLA. label Aug 24, 2019
@knative-prow-robot
Copy link
Contributor

Hi @Welkie. Thanks for your PR.

I'm waiting for a knative member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@knative-prow-robot knative-prow-robot added needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Aug 24, 2019
@mattwelke mattwelke changed the title Updated C# hello-world sample to multistep build, removed .dockerigno… [Sample] Update C# hello world according to Microsoft docs, to multistep build Aug 25, 2019
@mattwelke mattwelke changed the title [Sample] Update C# hello world according to Microsoft docs, to multistep build [Sample] Update C# hello world serving sample according to Microsoft docs, to multistep build Aug 25, 2019
@grayside
Copy link
Contributor

Hi Welkie, thanks for the PR!

I'm not familiar enough with C# to evaluate the practice here but in looking at the linked article, it makes sense.

Two minor points of feedback:

  1. Please restore the .dockerignore file, as it's purpose is to help ensure deterministic builds regardless of what happens in local development or changes to the Dockerfile.
  2. Please restore the comments in the Dockerfile, as they provided a bit more context and had consistency of more formal grammar across the sample code.

I see this change also switches the Container Registry away from Docker Hub. I'm not sure if there is a policy on this in the knative project, however, the comment referring to the container URL in Docker Hub seems like it should be updated if this is kept.

/assign grayside
/ok-to-test

@knative-prow-robot knative-prow-robot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Aug 27, 2019
…est of samples. Change link in Dockerfile to point to Microsoft site, not Docker Hub.
@mattwelke
Copy link
Contributor Author

mattwelke commented Aug 28, 2019

@grayside

Changes made. The comments should reflect the rest of the samples now.

Note that the reason I originally linked to the Docker Hub page at the top of the Dockerfile is because that still appears to be how Microsoft intends people to "discover" the image.

https://hub.docker.com/_/microsoft-dotnet-core-aspnet/

You can see how they give a sample docker pull command that grabs the image from the registry mcr.microsoft.com. It's a bit odd because usually if an image is listed on Docker Hub it's downloaded from Docker Hub too. I've updated the Dockerfile comment to have a link to the Microsoft docs page as you requested.

@grayside
Copy link
Contributor

Hi Welkie, thanks for making the changes. If Microsoft prefers to direct people to Docker Hub, I'm okay with keeping that link. Can we add a similar link for the second stage? Also, the README needs to be updated to match the Dockerfile.

Sorry for asking for so many minor changes! I've tested the new Dockerfile locally and this works.

…ch stage of build. Updated README.md file to reflect new Dockerfile.
@mattwelke
Copy link
Contributor Author

@grayside No problem. This should be good now. It's got the link at the top of each stage of the build in the Dockerfile, and they're Docker Hub links. The readme is up to date now too.

@mattwelke
Copy link
Contributor Author

@grayside Ready for a review. Made the changes you requested and included a fix for an issue @PicardParis caught.

@grayside
Copy link
Contributor

grayside commented Sep 5, 2019

/lgtm

@knative-prow-robot knative-prow-robot added the lgtm Indicates that a PR is ready to be merged. label Sep 5, 2019
@mattwelke
Copy link
Contributor Author

Do you need me to integrate the latest changes on the base branch before this can be merged?

@samodell
Copy link
Contributor

/approved

Sorry for the wait, @mattwelke ! Thanks for your contribution.

@samodell
Copy link
Contributor

I meant --

/approve

@knative-prow-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mattwelke, samodell

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@knative-prow-robot knative-prow-robot merged commit 533e6b7 into knative:master Sep 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cla: yes Indicates the PR's author has signed the CLA. lgtm Indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants