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 Error when enabling for an app. #330

Closed
jbosse opened this issue May 18, 2024 · 1 comment
Closed

Read-only File System Error when enabling for an app. #330

jbosse opened this issue May 18, 2024 · 1 comment

Comments

@jbosse
Copy link

jbosse commented May 18, 2024

Description of problem

I am honestly not sure where in the stack this problem lies, but since this is the only command that is failing this is where I will start.

How reproducible

It is now happening for all my apps, including apps that have already been configured.

Steps to Reproduce

  1. run dokku letsencrypt:enable reckless-embermine

Actual Results

jbosse@server:~$ dokku letsencrypt:enable reckless-embermine
=====> Enabling letsencrypt for reckless-embermine
-----> Enabling ACME proxy for reckless-embermine...
-----> Setting temporary site
-----> Getting letsencrypt certificate for reckless-embermine via HTTP-01
        - Domain 'reckless-embermine.jobo.dev'
docker: Error response from daemon: error while creating mount source path '/var/lib/dokku/data/letsencrypt/reckless-embermine': mkdir /var/lib/dokku: read-only file system.
-----> Certificate retrieval failed!
-----> Disabling ACME proxy for reckless-embermine...
 !     Failed to setup letsencrypt
 !     Check log output for further information on failure

Expected Results

Certificate created successfully.

Environment Information

dokku report reckless-ember mine output

dokku report reckless-ember mine GIST

How (deb/make) and where (AWS, VirtualBox, physical, etc.) was Dokku installed?:

wget -NP . https://dokku.com/bootstrap.sh
sudo DOKKU_TAG=v0.34.4 bash bootstrap.sh

Additional information

@jbosse
Copy link
Author

jbosse commented May 18, 2024

oh ffs. sudo apt upgrade resolved the problem.

@jbosse jbosse closed this as completed May 18, 2024
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

1 participant