Docker Desktop 4.33.0

Docker Desktop
1

I recently updated to DD 4.33.0 and now I’m having a challenge starting my containers. I can start a container and after 5-6 seconds it stops with a status of Exited(1). It doesn’t matter which container all show the same Exited(1) status.

If I run “Docker ps -a” I can see the Container IDs and etc.

I have tried running "Docker run -it with and without /bin/bash and receive an error “Unable to find image ‘containerID:latest’ locally”. I also tried "Docker start : It starts but after 5-6 seconds stops with a status of Exited(1).

I have not found anything in the log file that would give me a clue as to the challenge.

Your suggestions are appreciated.

OS: Mac ARM with DD Linux running MS SQL Server: 2022 latest

2

In order to understand your situation, we need some context information.

Please share the output of this command:

docker info

Furthermore, we need the exact docker run command, or if docker compose or docker stack deploy was used the content of the compose file. If a Dockerfile is used, please share its content as well.

When you share the outputs, always format your posts according to the following guide: How to format your forum posts

3

Meyay,

Last login: Mon Aug  5 06:24:52 on ttys000
admin@Laptop ~ % docker info
Client:
 Version:    27.1.1
 Context:    desktop-linux
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.16.1-desktop.1
    Path:     /Users/admin/.docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.29.1-desktop.1
    Path:     /Users/admin/.docker/cli-plugins/docker-compose
  debug: Get a shell into any image or container (Docker Inc.)
    Version:  0.0.34
    Path:     /Users/admin/.docker/cli-plugins/docker-debug
  desktop: Docker Desktop commands (Alpha) (Docker Inc.)
    Version:  v0.0.14
    Path:     /Users/admin/.docker/cli-plugins/docker-desktop
  dev: Docker Dev Environments (Docker Inc.)
    Version:  v0.1.2
    Path:     /Users/admin/.docker/cli-plugins/docker-dev
  extension: Manages Docker extensions (Docker Inc.)
    Version:  v0.2.25
    Path:     /Users/admin/.docker/cli-plugins/docker-extension
  feedback: Provide feedback, right in your terminal! (Docker Inc.)
    Version:  v1.0.5
    Path:     /Users/admin/.docker/cli-plugins/docker-feedback
  init: Creates Docker-related starter files for your project (Docker Inc.)
    Version:  v1.3.0
    Path:     /Users/admin/.docker/cli-plugins/docker-init
  sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.)
    Version:  0.6.0
    Path:     /Users/admin/.docker/cli-plugins/docker-sbom
  scout: Docker Scout (Docker Inc.)
    Version:  v1.11.0
    Path:     /Users/admin/.docker/cli-plugins/docker-scout

Server:
 Containers: 6
  Running: 1
  Paused: 0
  Stopped: 5
 Images: 9
 Server Version: 27.1.1
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Using metacopy: false
  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 splunk syslog
 Swarm: inactive
 Runtimes: runc io.containerd.runc.v2
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 2bf793ef6dc9a18e00cb12efb64355c2c9d5eb41
 runc version: v1.1.13-0-g58aa920
 init version: de40ad0
 Security Options:
  seccomp
   Profile: unconfined
  cgroupns
 Kernel Version: 6.10.0-linuxkit
 Operating System: Docker Desktop
 OSType: linux
 Architecture: aarch64
 CPUs: 8
 Total Memory: 7.655GiB
 Name: docker-desktop
 ID: 50ee6983-2283-4bf6-a7fc-ab2d0f03498b
 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
 Labels:
  com.docker.desktop.address=unix:///Users/admin/Library/Containers/com.docker.docker/Data/docker-cli.sock
 Experimental: false
 Insecure Registries:
  hubproxy.docker.internal:5555
  127.0.0.0/8
 Live Restore Enabled: false

WARNING: daemon is not using the default seccomp profile
admin@Laptop ~ % 

docker run --hostname=d3e5d9868231 --user=mssql --env=PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin --env=MSSQL_RPC_PORT=135 --env=CONFIG_EDGE_BUILD= --env=MSSQL_PID=developer --volume=Production:/var/opt/mssql/data --network=bridge -p 4553:1433 --restart=no --label='com.microsoft.product=Microsoft SQL Server' --label='com.microsoft.version=16.0.4105.2' --label='org.opencontainers.image.ref.name=ubuntu' --label='org.opencontainers.image.version=22.04' --label='vendor=Microsoft' --runtime=runc -d mcr.microsoft.com/mssql/server:2022-latest
4

This command looks generated, rather than what you actually used to create the container.
There are arguments included no one would actually specify, and environment variables missing that are required for the image.

According https://mcr.microsoft.com/en-us/product/mssql/server/about, the most simple configuration looks like this:

docker run -e "ACCEPT_EULA=Y"  \
  -e "MSSQL_SA_PASSWORD=yourStrong(!)Password" \
  -p 1433:1433 \
  -d mcr.microsoft.com/mssql/server:2022-latest

I am pretty sure that the container logs would indicate the container fails starting because you didn’t specify those mandatory parameters.

5

Meyay,

I originally started with the simple configuration using with

docker run -e "ACCEPT_EULA=Y" -e "MSSQL_SA_PASSWORD=VeryStr0ngP@ssw0rd" -p 4533:1433 --name sqlDB --hostname sqlDB --platform linux/amd64 -v "/Users/Admin/Docker/sqlDB/:/var/opt/mssql/data" -d mcr.microsoft.com/mssql/server:2022-latest

I then decided to use Docker Desktop Volumes in order preserve important files on the host in case DD had a challenge. I utilize a backup extension name “Volumes Backup & Share” so I do have backups.

I have been running DD for the last 9 months without any challenges and starting the container by entering the DD container page>selecting the appropriate container>Actions>Start. I updated to DD 4.33.0 the other day and that is when my challenges started: after clicking on Actions>Start, the status changes to running. Wait 5-6 seconds and then the status changes to Exited(1).

I tried using a Terminal command for the Docker run I posted and it errored:
WARNING: The requested image’s platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested.

6

Meyay,

I got it to work.

  1. I pulled down the latest image of mcr. microsoft.com / mssql/server:2022-latest
  2. Restored from my backup and let the system name the container
  3. Deleted the offending/bad containers
  4. Renamed the system generated container to what I wanted.

Thanks for responding to my inquiry.

8

What is your macOS version? When I try the command on my macOS Sonoma 14.5, it just works (with a valid password)