Container permissions errors in Colima 0.6.9

[ChaseWagoner]

Description

A container created from mcr.microsoft.com/azure-sql-edge:latest runs successfully when using a colima 0.6.8 instance, but not when using a colima 0.6.9 instance.

Version

colima version 0.6.9 git commit: c3a31ed05f5fab8b2cdbae835198e8fb1717fd0f

runtime: docker arch: aarch64 client: v26.1.4 server: v24.0.9 limactl version 0.22.0 qemu-img: unrecognized option '--version.' Try 'qemu-img --help' for more information

$ qemu-img --help qemu-img version 9.0.1

Operating System

• [ ] macOS Intel <= 13 (Ventura)
• [ ] macOS Intel >= 14 (Sonoma)
• [ ] Apple Silicon <= 13 (Ventura)
• [X] Apple Silicon >= 14 (Sonoma)
• [ ] Linux

Output of colima status

INFO[0000] colima is running using QEMU INFO[0001] arch: aarch64 INFO[0001] runtime: docker INFO[0001] mountType: sshfs INFO[0001] socket: unix:///Users/chase.wagoner/.colima/default/docker.sock

Reproduction Steps

Follow these steps with colima version 0.6.8, then version 0.6.9:

1. colima delete; colima start
2. docker run -e 'ACCEPT_EULA=Y' -e 'MSSQL_SA_PASSWORD=P@ssw0rd' -p 1433:1433 mcr.microsoft.com/azure-sql-edge:latest

With 0.6.8, the container runs and the DB engine is reachable. With 0.6.9, the container exits with errors. A selection of errors from the container logs is under Additional context.

Expected behaviour

The container starts successfully.

Additional context

The colima 0.6.8..0.6.9 diff shows the update of colima-core, which includes major version changes to Docker and Ubuntu. I vaguely suspect that the errors could relate to Ubuntu 24's security changes (release notes), but candidly I haven't investigated any farther than that, and likely cannot.

Container error logs A selection of logs from the container that I started after the colima 0.6.9 instance:

This program has encountered a fatal error and cannot continue running at Mon Jun 17 22:32:35 2024
The following diagnostic information is available:

         Reason: 0x00000001
         Signal: SIGABRT - Aborted (6)
          Stack: [omitted for brevity]
        Process: 24 - sqlservr
         Thread: 91 (application thread 0x100)
    Instance Id: ccefe5e1-3d65-46f4-aa80-aa1f3c9bcfb4
       Crash Id: fdf2f510-0832-467b-b372-be2ea85fbc22
    Build stamp: 7e3b976a7614e3cb6d16ce08aa8e3b28924df7f1870dfe9956e396a15452340b
   Distribution: Ubuntu 18.04.6 LTS aarch64
     Processors: 2
   Total Memory: 2051334144 bytes
      Timestamp: Mon Jun 17 22:32:35 2024
     Last errno: 2
Last errno text: No such file or directory

...

/bin/cat: /proc/24/environ: Permission denied
# hundreds of these errors:
/usr/bin/find: '/proc/24/task/24/fdinfo': Permission denied
/usr/bin/find: '/proc/24/task/25/fdinfo': Permission denied
/usr/bin/find: '/proc/24/map_files': Permission denied
/usr/bin/find: '/proc/24/fdinfo': Permission denied

...

dmesg: read kernel buffer failed: Operation not permitted
/usr/bin/timeout: failed to run command '/bin/journalctl': No such file or directory
/usr/bin/timeout: failed to run command '/bin/journalctl': No such file or directory

[zahid-ifap]

Is there an update for this issue I am facing the same thing

[abiosoft]

If you're trying to mssql server, I would recommend using macOS virtualization.framework with Rosetta.

# delete existing instance
colima delete

# create new instance with vz and rosetta
colima start --vm-type=vz --vz-rosetta