Selfhosted

44837 readers

1153 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago

MODERATORS

[email protected]

Caddy reverse proxy (lemmy.world)

submitted 6 days ago by [email protected] to c/[email protected]

17 comments fedilink hide all child comments

I 'm trying to setup a caddy reverse proxy within Docker and I am following the guide in this YouTube video

https://www.youtube.com/watch?v=qj45uHP7Jmo but when I the run docker compose up -d command I get this error:

failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error mounting "/home/Joe/container/caddy/Caddyfile" to rootfs at "/etc/caddy/Caddyfile": create mountpoint for /etc/caddy/Caddyfile mount: cannot create subdirectories in "/var/lib/docker/overlay2/49e15938cd9c418a331b963f6fbbd3bba726b28748113ee8d028f6adf034b525/merged/etc/caddy/Caddyfile": not a directory: unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type

I am a bit perplexed on what I am doing wrong so any advice would be appreciated!

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 6 points 6 days ago (1 children)

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:

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
```

Ensure correct permissions

chmod 644 /home/Joe/container/caddy/Caddyfile

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

Restart Docker and Try Again

docker compose down
docker compose up -d

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

[–] [email protected] 11 points 6 days ago

Seems like AI wrote this. And did a good job!