Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Read-only file system after installation completed #26

Open
sp1d3rino opened this issue Aug 2, 2018 · 1 comment
Open

Read-only file system after installation completed #26

sp1d3rino opened this issue Aug 2, 2018 · 1 comment

Comments

@sp1d3rino
Copy link

I installed as described for persistent option, but when I try to do installation of gogs I see this error

...: open /etc/gogs/conf/app.ini.265302332.tmp: read-only file system
infact if I try to login on docker process on the minishift machine I notice that /etc/gogs/conf is read only when I try to do for instance touch file1.

I don't understand where is the problem I can see in the storage that the gog-data is claimed on a persistentVolume in RWO and the /etc/gogs/conf is mounted on gog-data... so what is the problem here?

@Javatar81
Copy link

Gogs tries to write the tmp ini file into /etc/gogs/conf but this folder is mounted in a read-only config map. To solve this problem remove the config map (and create a volume claim mount instead).

The drawback with this approach is that you cannot edit the app.ini file directly over config map. Instead you can edit it from a terminal.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants