Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Failed to save key on readonly filesystem #29357

Closed
@mnapoli

Description

@mnapoli

Symfony version(s) affected: 4.1.4

Description

I run Symfony on a readonly filesystem and I can see this in my logs:

[warning] Failed to save key "%5BSymfony%5CBundle%5CFrameworkBundle%5CController%5CRedirectController%5D%5B1%5D" (array)
[warning] Failed to save key "%5BSymfony%5CBundle%5CFrameworkBundle%5CController%5CRedirectController%23urlRedirectAction%5D%5B1%5D" (array)

The urlRedirectAction is interesting, it seems like the routing might be caching a redirect response?

Am I doing something wrong here? I though the cache could be generated once (before deploying) and be readonly.

How to reproduce

I would say deploy Symfony (with its cache generated) on a readonly filesystem. I deployed Symfony 4 with Bref and its Symfony integration on AWS Lambda for example.

Possible Solution

Additional context

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions