"attempt to write a readonly database" in ghcr.io/openflagr/flagr container

[pdonovan-merit]

After creating an instance of ghcr.io/openflagr/flagr 1.1.14, attempting to create a new flag results in "attempt to write a readonly database"

Attempting write operations on the demo flag yields the same result.

Expected Behavior

As with 1.1.13, we expect the UI to allow us to add and modify flags. The application/image does appear to work correctly with that version.

Current Behavior

This error is produced when we try to add a new flag.

Possible Solution

Steps to Reproduce (for bugs)

1. Create and start a new instance of ghcr.io/openflagr/flagr:latest (1.1.14)
2. Attempt to add a flag called "test"

Context

Your Environment

• Version used (flagr version):
• Server type and version:
• Operating System and version (uname -a):
• Link to your project:

[michaeljs1990]

This can be closed out. Guess github doesn't let you close out multiple tickets with one Closes or I just did it wrong.

[ajbogh]

@michaeljs1990 this might not have been published yet. Is that possible to do, or is there a workaround for this with 1.1.14?

[ajbogh]

@zhouzhuojie this build requires your approval for the heroku deployment. Can you do this? It's currently blocking people from using the docker instance since the sqlite database is readonly. I've tried several workarounds without luck.

https://github.com/openflagr/flagr/actions/runs/3205461667/jobs/5238010792