compose-cli

compose-cli copied to clipboard

Description

When I run docker context create aci azurecontext, I get the response "no subscriptions found". I'm able to create new containers with az container create, and az account list -o table shows my subscription:

Name                         CloudName          SubscriptionId                        State    IsDefault
---------------------------  -----------------  ------------------------------------  -------  -----------
Azure Government Enterprise  AzureUSGovernment  4dae566e-*******************************  Enabled  True

Steps to reproduce the issue: 1.Run docker context create aci azurecontext

Describe the results you received:

no subscriptions found

Describe the results you expected: The creation of a context into which I could deploy containers.

Additional information you deem important (e.g. issue happens only occasionally): I'm on the Azure Gov Cloud. I tried passing my --tenant-id and --subscription-id directly in the docker context create aci command, same result. This is on Windows, with Docker Desktop (but I'm using the command prompt).

Output of docker-compose --version:

Docker Compose version v2.6.1

Output of docker version:

Client:
 Cloud integration: v1.0.24
 Version:           20.10.17
 API version:       1.41
 Go version:        go1.17.11
 Git commit:        100c701
 Built:             Mon Jun  6 23:09:02 2022
 OS/Arch:           windows/amd64
 Context:           default
 Experimental:      true

Server: Docker Desktop 4.10.1 (82475)
 Engine:
  Version:          20.10.17
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.17.11
  Git commit:       a89b842
  Built:            Mon Jun  6 23:01:23 2022
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.6.6
  GitCommit:        10c12954828e7c7c9b6e0ea9b0c02b01407d3ae1
 runc:
  Version:          1.1.2
  GitCommit:        v1.1.2-0-ga916309
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

Output of docker context show:
You can also run docker context inspect context-name to give us more details but don't forget to remove sensitive content.

default

Output of docker info:

Client:
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc., v0.8.2)
  compose: Docker Compose (Docker Inc., v2.6.1)
  extension: Manages Docker extensions (Docker Inc., v0.2.7)
  sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc., 0.6.0)
  scan: Docker Scan (Docker Inc., v0.17.0)

Server:
 Containers: 0
  Running: 0
  Paused: 0
  Stopped: 0
 Images: 0
 Server Version: 20.10.17
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Native Overlay Diff: true
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Cgroup Version: 2
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 io.containerd.runtime.v1.linux runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 10c12954828e7c7c9b6e0ea9b0c02b01407d3ae1
 runc version: v1.1.2-0-ga916309
 init version: de40ad0
 Security Options:
  seccomp
   Profile: default
  cgroupns
 Kernel Version: 5.10.104-linuxkit
 Operating System: Docker Desktop
 OSType: linux
 Architecture: x86_64
 CPUs: 2
 Total Memory: 1.447GiB
 Name: docker-desktop
 ID: RPHJ:5XN5:UYDM:6IX6:UMBE:LOWO:UXFW:QVGK:LPCU:XZ2X:66TX:SCIY
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 HTTP Proxy: http.docker.internal:3128
 HTTPS Proxy: http.docker.internal:3128
 No Proxy: hubproxy.docker.internal
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: false
 Insecure Registries:
  hubproxy.docker.internal:5000
  127.0.0.0/8
 Live Restore Enabled: false

Additional environment details (AWS ECS, Azure ACI, local, etc.):

I figured this out by reading this issue, then this pull request and then inferring the flag I needed, --cloud-name:

docker login azure --cloud-name AzureUSGovernment

After I logged in again that way, I could create a context.

That PR notes "This PR does not include documentation changes" - it would be helpful if this was documented somewhere, I couldn't find it anywhere on Azure or Docker docs.

Actually I suppose I should leave this open until it's addressed via documentation fix.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

This issue has been automatically closed because it had not recent activity during the stale period.