Skip to content

Errors inside Docker container have Docker path, not host path #56185

Open
@martinbean

Description

@martinbean

Laravel Version

12.x

PHP Version

N/A

Database Driver & Version

No response

Description

I was investigating the built-in Laravel exception renderer. I discovered there’s an undocumented app.editor configuration value that when set, will add editor links to lines like the Spatie Ignition-powered error pages used to. However, the path it uses is the absolute path. So if running inside a Docker container (which I do for pretty all of my projects), it has the path to files inside the Docker, so clicking on them in an editor on my host machine outside of the Docker container fails, as the path is not the same on my host machine.

Ignition used to address this by allowing two environment variables to be set:

  • IGNITION_LOCAL_SITES_PATH
  • IGNITION_REMOTE_SITES_PATH

It would be nice if the Laravel framework could offer similar variables (or even just use this if they’re present) to map paths from paths inside containers to paths on the host machine.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions