I am facing a challenge with my dotnet core application that has authorization. Due to company policy restrictions, Bearer tokens cannot be stored on the front-end. To work around this, I want to utilize an MVC Controller. However, the application is built as a SPA using Vue.js, which generates an index.cshtml file. While this setup works fine locally in Kestrel, deploying it to a Docker container presents a problem. It seems like there might be a conflict between how MVC expects files to be located and how Docker handles them.
I have attempted different approaches to locate the file within the pod. The application runs in the /app directory, and the SPA was initially deployed to /app/wwwroot. Despite my efforts, I couldn't get the MVC Controller to read from that specific folder. Even changing the vue.js webpack configuration to output files under /app/View/[ControllerName] did not resolve the issue.
Dockerfile:
FROM microsoft/dotnet:2.2-aspnetcore-runtime
EXPOSE 80
# Create app directory
WORKDIR /app
# Copy files from the artifact staging folder on agent
COPY <ProjectName>/out .
RUN apt-get update -y && apt-get install ca-certificates -y && rm -rf /var/lib/apt/lists/*
ADD certificate.crt
ADD certificate2.crt
ADD certificate3.crt
RUN update-ca-certificates
ENTRYPOINT ["dotnet", "<ProjectName>.dll"]
Expected outcome: successful loading of the SPA. Actual results: encountering various MVC errors related to the inability to find the index.cshtml file in different directories. Despite my attempts to guide it to the right location (e.g., pointing to vue.js under /app/wwwroot or making sure the SPA is generated under /Views/[ControllerName]), the build process seems flawed, resulting in unexpected behaviors such as generating a non-existent HomeController in one instance.