https://pulumi.com logo
#general
Title
# general
m

millions-eve-97186

08/20/2021, 1:03 PM
Hi! I wonder if I am the only one getting unwarranted warnings as Pulumi creates Docker images. Details in ๐Ÿงต
Running on Windows 10 Pulumi v3.10.3 Docker version 20.10.7, build f0df350
Running 'pulumi up' on the aws-cs-fargate example (https://github.com/pulumi/examples/tree/master/aws-cs-fargate). Prints the following warning:
Diagnostics:
docker:image:Image (app-img):
warning: #1 [internal] load build definition from Dockerfile#1 sha256:efb73d9b9794ffc8cac1eaab81a349b29e7d7d5f8f0af2c175fdf486c7b337d7#1 transferring dockerfile: 32B done#1 DONE 0.0s#2 [internal] load .dockerignore#2 sha256:eac54f5bff85a939dd67169d763cb8c685c3062a97ad691346dbfcd033d3a49d#2 transferring context: 34B done#2 DONE 0.0s#3 [internal] load metadata for <http://mcr.microsoft.com/dotnet/core/aspnet:3.1#3|mcr.microsoft.com/dotnet/core/aspnet:3.1#3> sha256:6ed55082f004e08158b7de81c6d78949cd5140b3f2899e0f69981d4ae515675f#3 DONE 0.1s#4 [internal] load metadata for <http://mcr.microsoft.com/dotnet/core/sdk:3.1#4|mcr.microsoft.com/dotnet/core/sdk:3.1#4> sha256:b2e5e1691f8e48edebecccdb649a2de20dda9e0f52cc817f2e6ef4b3c09e2f63#4 DONE 0.1s#7 [build 1/6] FROM <http://mcr.microsoft.com/dotnet/core/sdk:3.1@sha256:aa984bf37de864afe9f34bc80e42412dd95702b94731a481821eeae364df77ae#7|mcr.microsoft.com/dotnet/core/sdk:3.1@sha256:aa984bf37de864afe9f34bc80e42412dd95702b94731a481821eeae364df77ae#7> sha256:275df731aa9c2218ab3c56b6bbafe4565bcb61d7d3d328cbecf97669d887c08d#7 DONE 0.0s#5 [stage-1 1/3] FROM <http://mcr.microsoft.com/dotnet/core/aspnet:3.1@sha256:9280563285e34929fdae56b8759d8050169b3ce125a5dced64945b3b51e79918#5|mcr.microsoft.com/dotnet/core/aspnet:3.1@sha256:9280563285e34929fdae56b8759d8050169b3ce125a5dced64945b3b51e79918#5> sha256:edd51765ad78b294943ffa57cd763066c47915bf533e5a2709c16dea00579e91#5 DONE 0.0s#9 [internal] load build context#9 sha256:e2e1d5172e1b4e003924b303ebb2e83242ae3b3ffc2c5b1343bf12567603b833#9 transferring context: 310B done#9 DONE 0.0s#6 [stage-1 2/3] WORKDIR /app#6 sha256:0dba978db97424e5b85419e0c97334e21bb09678caca17f462a4d759271e1436#6 CACHED#13 [build 6/6] RUN dotnet publish -c release -o /app/bin --no-restore#13 sha256:a7dbd7ad3ef930c4aa5c75caa82ea22b1b4372a9c43c044bc025cf22760170c0#13 CACHED#11 [build 4/6] RUN dotnet restore#11 sha256:766fb7d1623cde52016f7bbd8918b97a3268ffc68201208712e79effea2abdd8#11 CACHED#8 [build 2/6] WORKDIR /app/src#8 sha256:7bc35ac3a7206e254b52e6e0ef1e2158831ea705814eeedf08642c5f798b98a7#8 CACHED#10 [build 3/6] COPY *.csproj .#10 sha256:29116e664bf51f077de97908349408b584f5fb22db6960af78647cef58499729#10 CACHED#12 [build 5/6] COPY * ./#12 sha256:49938a4c71c8176b828ea5ddc20e113c09ef43825b57bc1a668d424bc58babb5#12 CACHED#14 [stage-1 3/3] COPY --from=build /app/bin ./#14 sha256:19fa4e67c5c43ef422ff4fc9d201923a71320415efef15c1fe8f9759b78ecee3#14 CACHED#15 exporting to image#15 sha256:e8c613e07b0b7ff33893b694f7759a10d42e180f2b4dc349fb57dc6b71dcab00#15 exporting layers done#15 writing image sha256:d0f2de717bdfed9af2fed35a390b3f24759031867345043ca8a5035880c738b0 done#15 naming to <http://875536617367.dkr.ecr.eu-north-1.amazonaws.com/app-repo-a6a217d|875536617367.dkr.ecr.eu-north-1.amazonaws.com/app-repo-a6a217d> done#15 DONE 0.0s
Pic for a more nice format
As far as I can tell, this is not really a warning. Only Docker output.
๐Ÿ‘ 1
Is this the way it works for everyone, or do I have some kind of local environment deviation on my machine?
a

acoustic-window-73051

08/20/2021, 2:11 PM
Dont know, I built a wrapper for my docker image builds
but it does look like normal docker. output
m

millions-eve-97186

08/23/2021, 11:49 AM
@acoustic-window-73051 thx for input. I'm not really concerned. But it would be nice to have tools that give reliable warnings. Using utils that provides warnings that you learn to ignore is a bit of a bad habit ๐Ÿ™‚
๐Ÿ’ฏ 1