This is how I've prepared my Dockerfile: FROM node:16įonts-ipafont-gothic fonts-wqy-zenhei fonts-thai-tlwg fonts-kacst fonts-freefont-ttf libxss1 \ So first to get the id of the container: docker ps, and once we have the id of the container: docker exec -it CONTAINER_ID /bin/bash.Installing puppeteer NPM package directly won't work for some reason and sadly the official Puppeteer documentation in GitHub is not compatible with arm64 architecture. Well, since this is running under docker (and this is just a hobby app, I’m using old-school rolling file logs), I actually need to sh into the container first to see the logs. So far so good! But after invoking one of the reports yields an internal server error. Then I run a container using docker run -p 127.0.0.1:80:80/tcp myimage. Hence why I’m using the solution directory when we build the image. Note that in order for the build step in the docker file to work, the image has to be created at the solution level and not the project level - since all of the projects need to be built. Then I build an image using docker build -t myimage -f. # Set the directory back so dotnet is able to run the applicationīasically, I load the ASP.NET 6 base image, build the solution, publish it, install require node modules and set the dotnet program as the entry point of the container. RUN dotnet publish "" -c Release -o /app/publishĮNTRYPOINT RUN dotnet build "" -c Release -o /app/build FROM /dotnet/aspnet:6.0 AS baseįROM /dotnet/sdk:6.0 AS buildĬOPY
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |