ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
I get the error: failed to solve with frontend dockerfile.v0: failed to create LLB definition: no match for platform in manifest when building the following Dockerfile: FROM mcr.microsoft.com/dotnet/framework/aspnet:4.8 COPY . /inetpub/wwwroot
Asked · Aug 30
answered · Aug 30
Given this Dockerfile : FROM docker.io/alpine RUN mkdir test # RUN umask 0022 COPY README /test/README COPY --chmod=777 README /test/README-777 COPY --chmod=755 README /test/README-755 COPY FORALL /test/FORALL COPY --chmod=777 FORALL /test/FORALL-777 COPY --chmod=755 FORALL /test/FORALL-755 RUN ls -la /test I'd expect to have the read , write , execute permi
In the past I could simply do something like this: Dockerfile : FROM ubuntu RUN echo "test" which would output test to my shell. I used this as a way of debugging my builds. In the latest stable version of docker for windows the build output looks completely different and is not showing any stdout from any command. How can I see the output of any command in
Snippet from my Dockerfile : FROM node:12.18.0 RUN echo "hello world" RUN psql --version When I run docker build . I don't see any output from these two commands even if they are not cached. The documentation says that docker build is verbose by default. Why am I not seeing the output from commands? I used to see them before. The output while building: =>
docker