Skip to content
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

Add Dockerfile for AssetAdmistrationShellRepository #2

Open
bjoernhoeper opened this issue Jan 28, 2022 · 2 comments
Open

Add Dockerfile for AssetAdmistrationShellRepository #2

bjoernhoeper opened this issue Jan 28, 2022 · 2 comments

Comments

@bjoernhoeper
Copy link

The Registry Server is already dockerized but a Dockerfile for the AssetAdministrationShellRepository is not yet implemented.

@HansG89
Copy link

HansG89 commented Mar 18, 2022

All of the basyx dotnet applications can be dockerized in the same way, by simply adding a Dockerfile like this:

FROM mcr.microsoft.com/dotnet/sdk:6.0 AS build
WORKDIR /src
COPY AasServer.csproj .
RUN dotnet restore AasServer.csproj
COPY .
RUN dotnet publish AasServer.csproj -c Release -o /app/publish

FROM mcr.microsoft.com/dotnet/aspnet:6.0 AS runtime
WORKDIR /app
COPY --from=build /app/publish .
EXPOSE 5998
ENTRYPOINT ["dotnet", "AasServer.dll"]

@bjoernhoeper
Copy link
Author

Yes I know but I think there should be one file for each of these in the repository. So the issue is more a work item to do that. And when that is done I would propose to also automate building the images and pushing them to a central registry. Mainly to foster adaptation by other users.

All of the basyx dotnet applications can be dockerized in the same way, by simply adding a Dockerfile like this:

FROM mcr.microsoft.com/dotnet/sdk:6.0 AS build
WORKDIR /src
COPY AasServer.csproj .
RUN dotnet restore AasServer.csproj
COPY .
RUN dotnet publish AasServer.csproj -c Release -o /app/publish

FROM mcr.microsoft.com/dotnet/aspnet:6.0 AS runtime
WORKDIR /app
COPY --from=build /app/publish .
EXPOSE 5998
ENTRYPOINT ["dotnet", "AasServer.dll"]

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

No branches or pull requests

2 participants