Greetings, we are trying to run a pulumi deploy for dotnet inside of a Gitlab Runner Ci/Cd job. The running container is instanced via the docker+machine executor, and as such, runs a base image mcr.microsoft.com/dotnet/sdk:6.0 since we're building an aspnet service. All the AWS resources are generated correctly, however it seems to hang when publishing the image to ECR. The repository is created, however the pulumi up command just hangs. We've tried adding --verbose, but no other additional information is supplied other than the continuous addition of . for updating.... log. Are there any steps we can take to further diagnose the exact root of the issue? We have confirmed that running thus locally, it all functions as we expect.

Maximum verbosity is achieved by setting

-v=9

, and since you're running in CI, you'll want to add

--logtostderr

(otherwise the logs go to files which disappear with your build container..).

Got it. We'll try that. Is there a

pulumi/pulumi-dotnet

docker image that has .NET 6?

Hmm, the docs don't link to the Dockerfiles.. that's an oversight. Onesec I'll check GitHub.

Got it. Thanks for the update @little-cartoon-10569

Though isn't 3.1 the latest? I'm a bit out of the dotnet world these last few years..

The latest version of .NET Core is .NET 6. For more information, see the summary https://docs.microsoft.com/en-us/dotnet/core/whats-new/dotnet-6. They're trying to unify the sdks, which makes sense.

Ah. The page I looked at doesn't explain that at all well...

Yeah, hopefully this confusion will be a thing of the past now 😅

I think you're saying that your build script is running

docker

inside the GitLab-CI container?

docker

isn't installed by default iirc, you need to use the dind base image. Onesec, I'll get docs.

Yeah I had made some bad assumptions, which are now resolved. We are running our own instance of Gitlab with AWS autoscaling on the runners. I'll share the gitlab yml here as an example of how we worked around a few problems: 1. We're planning on generating a Dockerfile to change the default .NET version to 6, but for now we just install it as part of the job (for testing purposes). 2. We solved the docker communication issue by using docker:dind service to allow for communication to push the image.

services:
  - name: docker:20-dind
    alias: docker
    command: ["--tls=false"]

deploy:
    image: 
      name: pulumi/pulumi-dotnet
    when: manual
    tags:
      - docker
    variables:
      # AWS_ACCESS_KEY_ID supplied via CiCd variables...
      # AWS_SECRET_ACCESS_KEY supplied via CiCd variables...
      AWS_REGION: us-west-1
      PULUMI_PROJECT_DIR: ./Product.Pulumi
      PULUMI_CONFIG_PASSPHRASE: $CI_COMMIT_REF_NAME
      DOCKER_DRIVER: overlay2
      DOCKER_HOST: <tcp://docker:2375> 
      DOCKER_TLS_CERTDIR: ""
    script:
      # Prepre docker cli...
      - apt-get update && apt-get install -y ca-certificates && apt-get install -y curl && apt-get install -y gnupg && apt-get install -y lsb-release
      - curl -fsSL <https://download.docker.com/linux/debian/gpg> | gpg --dearmor -o /usr/share/keyrings/docker-archive-keyring.gpg
      - echo "deb [arch=$(dpkg --print-architecture) signed-by=/usr/share/keyrings/docker-archive-keyring.gpg] <https://download.docker.com/linux/debian> $(lsb_release -cs) stable" | tee /etc/apt/sources.list.d/docker.list > /dev/null
      - apt-get update && apt-get install -y docker-ce-cli
      # Install dotnet 6, will eventually bake this in our own pulumi docker image...
      - apt-get install -y wget
      - wget <https://dot.net/v1/dotnet-install.sh>
      - bash dotnet-install.sh -c Current
      # Login to our S3 backend to store / restore state...
      - pulumi login <s3://our-product-backend-bucket/$CI_COMMIT_REF_NAME>
      # Deploy...
      - cd $PULUMI_PROJECT_DIR
      - pulumi stack select $CI_COMMIT_REF_NAME --create --verbose 9
      - pulumi up --stack $CI_COMMIT_REF_NAME --non-interactive --yes --skip-preview --verbose 9

Hopefully someone finds this useful if they run into a similar issue.