Permission denied on /home/user/.exitbox-config/config.yaml — config directory not mounted into container

[batistein]

Describe the bug

Running exitbox run claude fails immediately with a permission error and the agent never starts.

To Reproduce

exitbox run claude -vv

Output:

[INFO] Starting Squid proxy...
/usr/local/bin/docker-entrypoint: line 136: /home/user/.exitbox-config/config.yaml: Permission denied
[INFO] Stopping Squid proxy (no running agents)...

Environment

• OS: Fedora
• SELinux: enforcing
• Container runtime: Podman (rootless)

Root Cause

The container entrypoint tries to write to /home/user/.exitbox-config/config.yaml, but this path is inside the image's read-only filesystem layer. The host directory ~/.exitbox-config is never bind-mounted into the claude container.

Inspecting the container after a failed run confirms only squid.conf is mounted — ~/.exitbox-config is absent:

"Mounts": [
  {
    "Type": "bind",
    "Source": "/home/myuser/.cache/exitbox/squid.conf",
    "Destination": "/etc/squid/squid.conf"
  }
]

Expected Behavior

~/.exitbox-config on the host should be bind-mounted into the container at /home/user/.exitbox-config, so config is persisted across runs and the entrypoint can write to it.

[thecodeassassin]

@batistein Please try out v0.2.0, should be fixed:

https://github.com/Cloud-Exit/ExitBox/releases/tag/v0.2.0

[batistein]

[INFO] Starting Squid proxy...
/usr/local/bin/docker-entrypoint: line 136: /home/user/.exitbox-config/config.yaml: Permission denied
[INFO] Stopping Squid proxy (no running agents)...
user@computer:~/mypath$ exitbox version
exitbox version v0.2.0

Still the same error in this environment