• 0 Posts
  • 4 Comments
Joined 1 month ago
cake
Cake day: February 15th, 2025

help-circle


  • The error suggests that you’re trying to mount a file (Caddyfile) onto a directory or vice versa. Let’s debug this step by step.

    Steps to Fix:

    1. Check if the path exists and is correct Run:

      ls -ld /home/Joe/container/caddy/Caddyfile
      
      • If it’s a directory, it should be a file instead.
      • If it doesn’t exist, create an empty one:
        touch /home/Joe/container/caddy/Caddyfile
        
    2. Ensure correct permissions

      chmod 644 /home/Joe/container/caddy/Caddyfile
      
    3. Check YAML Formatting
      Your docker-compose.yml seems to have incorrect indentation and improper quotes around version. Here’s a fixed version:

      version: "3.3"
      
      networks:
        caddy:
      
      services:
        portainer:
          image: portainer/portainer-ce:latest
          container_name: portainer2
          restart: unless-stopped
          security_opt:
            - no-new-privileges:true
          volumes:
            - /etc/localtime:/etc/localtime:ro
            - /var/run/docker.sock:/var/run/docker.sock:ro
            - /home/Joe/containers/portainer/portainer-data:/data
          networks:
            - caddy
          ports:
            - 9000:9000
      
        caddy:
          image: caddy:latest
          restart: unless-stopped
          container_name: caddy
          ports:
            - 80:80
            - 443:443
          volumes:
            - /home/Joe/container/caddy/Caddyfile:/etc/caddy/Caddyfile
            - /home/Joe/container/caddy/site:/srv
            - /home/Joe/container/caddy/caddy_data:/data
            - /home/Joe/container/caddy/caddy_config:/config
          networks:
            - caddy
      
    4. Restart Docker and Try Again

      docker compose down
      docker compose up -d
      

    If the error persists, check docker logs caddy for additional hints.


  • Probably should have given all of the evidence to the police instead of deleting some of it.

    In most western jurisdictions platform operators are not liable for user content, (as long as they cooperate with the authorities) so nothing for you to worry about.

    Next time, don’t do anything, no deleting, no blocking, contact the police and ask them what they would like you to do. Maybe they’d even would want to letting them keep posting for a while to gather more data on the offenders, but idk how they deal with selfhosted stuff tbh…

    (this is not legal advice)

    (Also I totally understand that you don’t want your other users seing that kind of stuff. I know nothing about the matrix moderation tools, so maybe the media is on the server db somewhere … might be relevant to figure that out)


    Edit: this does not apply if you live in an authoritarian police state or third world country, like OP apparently does.