Skip to content

update Dockerfile with dotnet 5.0#29

Merged
StefH merged 1 commit intowiremock:masterfrom
ibmer921150:patch-1
Dec 4, 2020
Merged

update Dockerfile with dotnet 5.0#29
StefH merged 1 commit intowiremock:masterfrom
ibmer921150:patch-1

Conversation

@ibmer921150
Copy link
Copy Markdown
Contributor

Hi there,

I am aware of the change commit 8b6ed90, the .net has been upgrade to 5.0 from 3.1. The dockerfile should be updated accordingly. If I still use the dotnet core 3.1 in the dockerfile. The build can be successfully. But the docker run will fail as below error with dotnet compatibility issue.

Commandline arguments are invalid. WireMock.Net cannot start.

Note that the dotnet core runtime only support Ubuntu 20 https://hub.docker.com/_/microsoft-dotnet-aspnet

Happy to discuss.

Thanks
Yu

Hi there, 

I am aware of the change commit 8b6ed90, the .net has been upgrade to 5.0 from 3.1. The dockerfile should be updated accordingly. If I still use the dotnet core 3.1 in the dockerfile. The build can be successfully. But the docker run will fail as below error with dotnet compatibility issue.

Commandline arguments are invalid. WireMock.Net cannot start.

Note that the dotnet core runtime only support Ubuntu 20 https://hub.docker.com/_/microsoft-dotnet-aspnet
@ibmer921150
Copy link
Copy Markdown
Contributor Author

ibmer921150 commented Dec 3, 2020

I have no chance to test the dotnet core 5.0 yet, the pull request would be a suggestion

@StefH
Copy link
Copy Markdown
Collaborator

StefH commented Dec 4, 2020

Hello @ibmer921150,

Thanks for reporting this.

The issue about Commandline arguments are invalid. WireMock.Net cannot start. was this error:
6b830f9#diff-6fbe11e848adfb7fc51116ca7809038ec1a2f769c9db9055e7d1fa427a874aedR15

However upgrading Linux to .NET 5 is a good idea.

@StefH StefH merged commit d86668b into wiremock:master Dec 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants