Have you tried `--progress=plain`?

Example:

    FROM alpine
    RUN ps aux

Relative output of `DOCKER_BUILDKIT=1 docker build --progress=plain -t test_buildkit .`:

    #5 [2/2] RUN ps aux
    #5       digest: sha256:e2e4ae1e7db9bc398cbcb5b0e93b137795913d2b626babb0f148a60017379d86
    #5         name: &quot;[2/2] RUN ps aux&quot;
    #5      started: 2019-04-19 09:02:58.922035874 +0000 UTC
    #5 0.693 PID   USER     TIME  COMMAND
    #5 0.693     1 root      0:00 ps aux
    #5    completed: 2019-04-19 09:02:59.721490002 +0000 UTC
    #5     duration: 799.454128ms


&#128073; Also, check the very useful answer by [@Cocowalla](https://stackoverflow.com/users/25758/cocowalla) below about `BUILDKIT_PROGRESS=plain`

As well as using `--progress=plain` on the command line, you can also set an environment variable:

`BUILDKIT_PROGRESS=plain`

I find this particularly useful for CI builds, where I *always* want the full log.

[`create-react-app` v3.0.0 is out](https://github.com/facebook/create-react-app/blob/master/CHANGELOG.md). It supports TypeScript linting internally. (That&#39;s nice!) I think I understand the situation where TSLint is on, and am planning to replace it with ESLint, but it is not right now.

How to disable that linting step in `react-scripts start`?


`/* eslint-disable */` and others are not the ones I&#39;m looking for.

Disable ESLint that create-react-app provides

I updated my ASP.NET Core project to .NET Core v3.0.0-preview3, and I now get:

&gt; Startup.cs(75,50,75,69): warning CS0618: &#39;IHostingEnvironment&#39; is
&gt; obsolete: &#39;This type is obsolete and will be removed in a future
&gt; version. The recommended alternative is
&gt; Microsoft.AspNetCore.Hosting.IWebHostEnvironment.&#39;

The code is:
```cs
public void Configure(IApplicationBuilder app, IHostingEnvironment env) {
  if (env.IsDevelopment()) {
    …
  }
}
```

What is the correct way to do this now? Are there any documentation or examples to demonstrate that?

&#39;IHostingEnvironment&#39; is obsolete

When building Docker images with `DOCKER_BUILDKIT=1`, there is a very cool progress indicator but no command output. How do I see the command output to debug my build?

When using BuildKit with Docker, how do I see the output of RUN commands?

<p>When building Docker images with <code>DOCKER_BUILDKIT=1</code>, there is a very cool progress indicator but no command output. How do I see the command output to debug my build?</p>


I am running Dotnet Core 2.2 in a Linux container in Docker.

I&#39;ve tried many different configuration/environment options - but I keep coming back to the same problem of running out of memory (&#39;docker events&#39; reports an OOM).


In production I&#39;m hosting on Ubuntu. For Development, I&#39;m using a Linux container (MobyLinux) on Docker in Windows.

I&#39;ve gone back to running the Web API template project, rather than my actual app. I am literally returning a string and doing nothing else. If I call it about 1,000 times from curl, the container will die. The garbage collector does not appear to be working at all.


Tried setting the following environment variables in the docker-compose:

    DOTNET_RUNNING_IN_CONTAINER=true
    DOTNET_SYSTEM_GLOBALIZATION_INVARIANT=true
    ASPNETCORE_preventHostingStartup=true


Also tried the following in the docker-compose:

    mem_reservation: 128m
    mem_limit: 256m
    memswap_limit: 256m

(these only make it die faster)

Tried setting the following to true or false, no difference:

    ServerGarbageCollection


I have tried instead running as a Windows container, this doesn&#39;t OOM - but it does not seem to respect the memory limits either.


I have already ruled out use of HttpClient and EF Core - as I&#39;m not even using them in my example. I have read a bit about listening on port 443 as a problem - as I can leave the container running idle all day long, if I check at the end of the day - it&#39;s used up some more memory (not a massive amount, but it grows).


Example of what&#39;s in my API:

    // GET api/values/5
    [HttpGet(&quot;{id}&quot;)]
    public ActionResult&lt;string&gt; Get(int id)
    {
    return &quot;You said: &quot; + id;
    }


Calling with Curl example:

    curl -X GET &quot;https://localhost:44329/api/values/7&quot; -H  &quot;accept: text/plain&quot; --insecure

(repeated 1,000 or so times)



Expected: RAM usage to remain low for a very primitive request

Actual: RAM usage continues to grow until failure



Full Dockerfile:

    FROM microsoft/dotnet:2.2-aspnetcore-runtime AS base
    WORKDIR /app
    EXPOSE 80
    EXPOSE 443

    FROM microsoft/dotnet:2.2-sdk AS build
    WORKDIR /src
    COPY [&quot;WebApplication1/WebApplication1.csproj&quot;, &quot;WebApplication1/&quot;]
    RUN dotnet restore &quot;WebApplication1/WebApplication1.csproj&quot;
    COPY . .
    WORKDIR &quot;/src/WebApplication1&quot;
    RUN dotnet build &quot;WebApplication1.csproj&quot; -c Release -o /app

    FROM build AS publish
    RUN dotnet publish &quot;WebApplication1.csproj&quot; -c Release -o /app

    FROM base AS final
    WORKDIR /app
    COPY --from=publish /app .
    ENTRYPOINT [&quot;dotnet&quot;, &quot;WebApplication1.dll&quot;]


docker-compose.yml

    version: &#39;2.3&#39;

    services:
      webapplication1:
        image: ${DOCKER_REGISTRY-}webapplication1
        mem_reservation: 128m
        mem_limit: 256m
        memswap_limit: 256m
        cpu_percent: 25
        build:
          context: .
          dockerfile: WebApplication1/Dockerfile


docker-compose.override.yml

    version: &#39;2.3&#39;

    services:
      webapplication1:
        environment:
          - ASPNETCORE_ENVIRONMENT=Development
          - ASPNETCORE_URLS=https://+:443;http://+:80
          - ASPNETCORE_HTTPS_PORT=44329
          - DOTNET_RUNNING_IN_CONTAINER=true
          - DOTNET_SYSTEM_GLOBALIZATION_INVARIANT=true
          - ASPNETCORE_preventHostingStartup=true
        ports:
          - &quot;50996:80&quot;
          - &quot;44329:443&quot;
        volumes:
          - ${APPDATA}/ASP.NET/Https:/root/.aspnet/https:ro
          - ${APPDATA}/Microsoft/UserSecrets:/root/.microsoft/usersecrets:ro


I&#39;m running Docker CE Engine 18.0.9.1 on Windows and 18.06.1 on Ubuntu. To confirm - I have also tried in Dotnet Core 2.1.

I&#39;ve also given it a try in IIS Express - the process gets to around 55MB, that&#39;s literally spamming it with multiple threads, etc.

When they&#39;re all done, it goes down to around 29-35MB.

Dotnet Core Docker Container Leaks RAM on Linux and causes OOM

This has been surprisingly confusing for me. I thought Docker&#39;s Image ID is its SHA256 hash. However, apparently the result from `docker image ls --digests` (listed under the column header `DIGEST`) is different from the `IMAGE ID` of that image.

For example

```
docker image ls --digests alpine
REPOSITORY          TAG                 DIGEST                                                                    IMAGE ID            CREATED             SIZE
alpine              latest              sha256:769fddc7cc2f0a1c35abb2f91432e8beecf83916c421420e6a6da9f8975464b6   055936d39205        2 weeks ago         5.53MB
```

while 

```
docker image ls --no-trunc
REPOSITORY                                             TAG                 IMAGE ID                                                                  CREATED             SIZE
...
alpine                                                 latest              sha256:055936d3920576da37aa9bc460d70c5f212028bda1c08c0879aedf03d7a66ea1   2 weeks ago         5.53MB
```

Clearly `sha256:055936d3920576da37aa9bc460d70c5f212028bda1c08c0879aedf03d7a66ea1` (IMAGE ID) and `sha256:769fddc7cc2f0a1c35abb2f91432e8beecf83916c421420e6a6da9f8975464b6` (DIGEST) are not the same value. But why? What&#39;s the purpose of having two different `sha256` hashes of the same image. How are they calculated, respectively?

I was confused by this when reading the book *Docker Deep Dive*, and I haven&#39;t been able to find a clear answer either in the book or online.

What&#39;s the difference between a Docker image&#39;s Image ID and its Digest?

I was following [this post][1] - the reference code is on [GitHub][2]. I have cloned the repository on my local.

The project has got a react app inside it. I&#39;m trying to run it on my local following **step 7** on the [same post][1]:

    docker run -p 8080:80 shakyshane/cra-docker

This returns:

    Unable to find image &#39;shakyshane/cra-docker:latest&#39; locally
    docker: Error response from daemon: pull access denied for shakyshane/cra-docker, repository does not exist or may require &#39;docker login&#39;.
    See &#39;docker run --help&#39;.

I tried login to docker again but looks like since it belongs to [@shakyShane][3] I cannot access it.

I idiotically tried `npm start` too but it&#39;s not a simple react app running on node - it&#39;s in the container and containers are not controlled by `npm`


Looks like `docker pull shakyshane/cra-docker:latest` throws this:

    Error response from daemon: pull access denied for shakyshane/cra-docker, repository does not exist or may require &#39;docker login&#39;

So the question is how do I run this docker image on my local mac machine?


  [1]: https://medium.com/@shakyShane/lets-talk-about-docker-artifacts-27454560384f
  [2]: https://github.com/shakyShane/cra-docker
  [3]: https://medium.com/@shakyShane

Unable to find docker image locally

I want to use docker compose with the host network. 

I have a docker container that access a local REST api.  Usually I run 

    docker run --net=host -p 18080:8080 -t -i containera

which can access the host REST api which runs at `http://127.0.0.1:8080`. Since I want to scale the container `containera` I found docker compose to scale the container. But the docker compose file from the [documentation](https://docs.docker.com/get-started/part3/) does not work. The docker container does not query the REST API. 

I tried the following compose file but the property



 

    version: &quot;3&quot;
    services:
      web:
        image: conatinera:latest
        network_mode: &quot;host&quot;
        deploy:
          replicas: 1
          resources:
            limits:
              cpus: &quot;0.5&quot;
              memory: 4G 
          restart_policy:
            condition: on-failure
        ports:
          - &quot;18080:8080&quot;


but the property `network_mode` is ignored/not allowed.  with the message 

    Ignoring unsupported options: network_mode



How to use host network for docker compose?

What is the right way for running multiple commands in one `action`?

## For example:

I want to run a python script as `action`. Before running this script I need to install the `requirements.txt`.

### I can think of several options:

 - Create a `Dockerfile` with the command `RUN pip install -r requirements.txt` in it.
 - Use the `python:3` image, and run the `pip install -r requirements.txt` in the `entrypoint.sh` file before running the arguments from `args` in `main.workflow`.
 - use both `pip install` and `python myscript.py` as `args`

## Another example:

I want to run a script that exists in my repository, then compare 2 files (its output and a file that already exists).

This is a process that includes **two commands**, whereas in the first example, the `pip install` command can be considered **a building command** rather than a test command.

## the question:

Can I create another Docker for another command, which will contain the output of the previous Docker?

I&#39;m looking for guidelines for the location of the command in `Dockerfile`, in `entrypoint` or in `args`.

How to run multiple commands in one Github Actions Docker

I tried `export DOCKER_BUILDKIT=1` before a `docker-compose build` command and I did not see the expected BuildKit output. What did I miss?

Content Type	Original Author	Original Content on Stackoverflow
Question	joeforker	View Question on Stackoverflow
Solution 1 - Docker	tgogos	View Answer on Stackoverflow
Solution 2 - Docker	Cocowalla	View Answer on Stackoverflow

When using BuildKit with Docker, how do I see the output of RUN commands?

Docker Problem Overview

Docker Solutions

Solution 1 - Docker

Solution 2 - Docker

'IHostingEnvironment' is obsolete

Disable ESLint that create-react-app provides

Attributions