liquibase data install fails

[rhinck]

When I try to run liquibase data install on my computer I get these errors.

####################################################
##   _     _             _ _                      ##
##  | |   (_)           (_) |                     ##
##  | |    _  __ _ _   _ _| |__   __ _ ___  ___   ##
##  | |   | |/ _` | | | | | '_ \ / _` / __|/ _ \  ##
##  | |___| | (_| | |_| | | |_) | (_| \__ \  __/  ##
##  \_____/_|\__, |\__,_|_|_.__/ \__,_|___/\___|  ##
##              | |                               ##
##              |_|                               ##
##                                                ## 
##  Get documentation at docs.liquibase.com       ##
##  Get certified courses at learn.liquibase.com  ## 
##  Free schema change activity reports at        ##
##      https://hub.liquibase.com                 ##
##                                                ##
####################################################
Starting Liquibase at 14:06:52 (version 4.7.0 #1140 built at 2022-01-07 19:26+0000)
Liquibase Version: 4.7.0
Liquibase Community 4.7.0 by Liquibase
Initializing titan infrastructure ...
Checking docker installation 100% │██████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████│ 100/100 (0:00:00 / 0:00:00) 
Starting titan server docker containers   2% │██▊                                                                                                                                            │   2/100 (0:00:00 / 0:00:10) 
Exception in thread "Thread-1" io.titandata.titan.exceptions.CommandException: Command failed: docker run --privileged --pid=host --network=host -d --restart always --name=titan-docker-launch -v /var/lib:/var/lib -v /run/docker:/run/docker -v /lib:/var/lib/titan-docker/system -v titan-docker-data:/var/lib/titan-docker/data -v /var/run/docker.sock:/var/run/docker.sock -e TITAN_PORT=49789 -e TITAN_IMAGE=titan:latest -e TITAN_IDENTITY=titan-docker titan:latest /bin/bash /titan/launch 
        at io.titandata.titan.utils.CommandExecutor.exec(CommandExecutor.kt:52)
        at io.titandata.titan.utils.CommandExecutor.exec$default(CommandExecutor.kt:30)
        at io.titandata.titan.clients.Docker.run(Docker.kt:160)
        at io.titandata.titan.clients.Docker.launchTitanServers(Docker.kt:99)
        at io.titandata.titan.providers.local.Install$install$5.invoke(Install.kt:44)
        at io.titandata.titan.utils.ProgressTracker$trackWithBar$thread$1.invoke(ProgressTracker.kt:42)
        at io.titandata.titan.utils.ProgressTracker$trackWithBar$thread$1.invoke(ProgressTracker.kt:41)
Starting titan server docker containers 100% │███████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████│ 100/100 (0:00:00 / 0:00:00)

Also Docker Desktop gives this error:

Error invoking remote method 'docker-start-container': Error: (HTTP code 500) server error - OCI runtime create failed: container_linux.go:380: starting container process caused: process_linux.go:545: container init caused: rootfs_linux.go:76: mounting "/var/lib/docker/volumes/titan-docker-data/_data" to rootfs at "/var/lib/titan-docker/data" caused: mkdir /var/lib/docker/overlay2/2e014e65643ccdeb11041a2a345471d6c2b198060f3a3cf861bcd11312ff5082/merged/var/lib/titan-docker: operation not permitted: unknown

I am running MacOS 12.2.1 on the M1 Max chip. Docker v4.5.0 (74594). Liquibase data v0.0.7

[mcred]

What's the output from docker run --rm -it --privileged --pid=host alpine:latest nsenter -t 1 -m -u -n -i awk '{ if ($1 == "kernel:") { inKernel = 1; next } if (inKernel == 1 && $1 == "image:") { print $2; inKernel = 0; quit } }' /etc/linuxkit.yml ?

[mcred]

I was just able to confirm that liquibase data works on MacOS 12.2.1 with the M1 chip. Can you check your docker desktop settings? Make sure that "Use gPRC FUSE for file sharing" is disabled. Example is available in the Session 1 tutorial.

[mcred]

@rhinck Are you able to confirm if this resolved your issue?