Need help urgently, next cloud install on macos with AIO was working for like 6 months before randomly failing out of nowhere

Docker Desktop
,
1

Welcome to Docker Extensions!

here is my compose file

services:
  nextcloud-aio-mastercontainer:
    image: ghcr.io/nextcloud-releases/all-in-one:beta
    init: true
    restart: always
    container_name: nextcloud-aio-mastercontainer # This line cannot be changed
    volumes:
      - nextcloud_aio_mastercontainer:/mnt/docker-aio-config
      - /var/run/docker.sock.raw:/var/run/docker.sock:ro
    networks:
      - nextcloud-aio
    ports:
      - 0.0.0.0:8080:8080
    environment:
      APACHE_PORT: 11000
      APACHE_IP_BINDING: 0.0.0.0
      SKIP_DOMAIN_VALIDATION: true
      OVERWRITEHOST: My domain ending with .ts.net which im not telling you
      OVERWRITEPROTOCOL: https

  caddy:
    build:
      context: .
      dockerfile: Caddy.Dockerfile
    depends_on:
      tailscale:
        condition: service_healthy
    restart: unless-stopped
    environment:
      NC_DOMAIN: Im not telling you # Change to your domain ending with .ts.net
    volumes:
      - type: bind
        source: ./Caddyfile
        target: /etc/caddy/Caddyfile
      - type: volume
        source: caddy_certs
        target: /certs
      - type: volume
        source: caddy_data
        target: /data
      - type: volume
        source: caddy_config
        target: /config
      - type: volume
        source: tailscale_sock
        target: /var/run/tailscale/ # Mount the volume for /var/run/tailscale/tailscale.sock
        read_only: true
    network_mode: service:tailscale

  tailscale:
    image: tailscale/tailscale:v1.82.0
    environment:
      TS_HOSTNAME: Im not telling you                      # Your tailnet hostname
      TS_AUTH_KEY: ${TS_AUTH_KEY}                            # Loaded from .env file
      TS_EXTRA_ARGS: --advertise-tags=tag:nextcloud # Required for OAuth client
    init: true
    healthcheck:
      test: tailscale status --peers=false --json | grep 'Online.*true'
      start_period: 3s
      interval: 1s
      retries: 3
    restart: unless-stopped
    devices:
      - /dev/net/tun:/dev/net/tun
    volumes:
      - type: volume
        source: tailscale
        target: /var/lib/tailscale
      - type: volume
        source: tailscale_sock
        target: /tmp # Mount entire /tmp folder to access tailscale.sock
    cap_add:
      - NET_ADMIN
    networks:
      - nextcloud-aio

volumes:
  nextcloud_aio_mastercontainer:
    name: nextcloud_aio_mastercontainer # This line cannot be changed
  caddy_certs:
  caddy_config:
  caddy_data:
  tailscale:
  tailscale_sock:

networks:
  nextcloud-aio:
    name: nextcloud-aio
    driver: bridge
    enable_ipv6: false
    driver_opts:
      com.docker.network.driver.mtu: "1280" # Can be set to 9001 for jumbo frames
      com.docker.network.bridge.host_binding_ipv4: "127.0.0.1" # Security hardening
      com.docker.network.bridge.enable_icc: "true"
      com.docker.network.bridge.default_bridge: "false"
      com.docker.network.bridge.enable_ip_masquerade: "true"

this is from the official macos aio guide on the next-cloud GitHub page Tailscale (and Caddy as a sidecar) Reverse Proxy · nextcloud/all-in-one · Discussion #5439 · GitHub all the other files in my directory where i used docker compose up -d are the same as in the guide with nothing changed, the only reason i changed some of the stuff here was to make it wok, for some reason Apache IP binding had to be 0.0.0.0 otherwise it wouldn’t work. A couple months later my mac-book dies because someone in my family accidentally stepped on the charger, and the battery drained slowly as i wouldn’t notice until i got back from McDonald. Leading it to be stuck on a black screen, while still technically being connected to the network, and having functionality besides audio and the display, I connected an external monitor, and now docker refuses to work with the error being “hypervisor check failed” My plan is to migrate the docker volumes from my MacBook to my Proxmox server, which still works, but I don’t know how to do that, any help would be appreciated, as I can’t find any other people in similar situations like me.

2

I have around 17 gb of files on nextcloud, with them being photos of trips across the world.

3

I’m not sure I understand everything. So you have a MacBook on which you run Docker Desktop and you run NextCoud in Docker Desktop, but now you get “hypervisor check failed” when you try to run Docker Desktop, right?

Just to confirm that we are not talking about running the containers after a successfully started Docker Desktop.

Since every container runs in the virtual machine of Docker Desktop, if there is a hypvervisor problem on Mac, you won’t be able to start Docker Desktop.

Please, help us to understand where exactly you get the error message. What do you run before that or where do you click?

Docker Desktop supports multiple virtualization methods, so in case only one fails, maybe we can try to manually activate the other, but if your filesystem is corrupted on Mac that somehow breaks virtualization entirely, you can still find the data disk. By default it is here:

/Users/ta/Library/Containers/com.docker.docker/Data/vms/0/data/Docker.raw

If that VM disk is not corrupted, you could try to save that and mount it somewhere, but I was not able to do it yet.

4

Before opening docker i run tailscale up, to ensure it is connected to my tailnet, and make sure the serve status is tailscale serve --bg http://localhost:11000 even with tailscale off it doesnt work. Ssh is also failing as i cant start docker there either, nor with an external monitor since my macbook decided to kill itself and not work with virtualizing. I was hoping for there to be a physical directory which i could copy over ssh. Im a bit a of a noob. Basically to clarify you have most of the information, and i want to try the other virtualization methods, which i can maybe enable over ssh, because the thing is macos doesnt support external monitors really well.

5

Unsupported extension

6

If you want to try another virtualization method, you can find the settings file here

cat "$HOME/Library/Group Containers/group.com.docker/settings-store.json"

It contains the following setting

"UseVirtualizationFramework": false,

The value is either false or true. If it is true, change it to false. If it is false, change it to true before trying to start Docker Desktop. This setting controlls whether you are using Apple’s virtualization framework or the beta “Docker VMM” made by Docker.

There are also two other parameters

  "UseVirtualizationFrameworkRosetta": false,
  "UseVirtualizationFrameworkVirtioFS": true

These matter only when “UseVirtualizationFramework” is true. You can try changing those as well.

I hope one of the combinatons of these parameters help.

8

everything works now, i originally charged my macbook for 1 day powered it on and off, but that didn’t do anything, so the day after that it charges, i press the boot button and option command pr again, and it works, after restarting all the containers everything worked

9

does anyone know why, when you connect an external monitor or start docker via ssh, it gives you a virtualization error? Maybe this can be fixed in the more recent docker updates?