Closed KRISCHOMAT closed 5 months ago
I got a similar issue after upgrading but with another permission error
chown: changing ownership of '/app/.release': Operation not permitted
Full deploy logs here https://github.com/jobbsy-dev/jobbsy/actions/runs/8505515648/job/23294121537
Mind checking if upgrading to Dokku 0.34.3 and Herokuish 0.9.1 helps?
Mind checking if upgrading to Dokku 0.34.3 and Herokuish 0.9.1 helps?
Upgraded to Dokku 0.34.3 but how to check Herokuish version and how to upgrade it if it's necessary?
You can check the herokuish version by running dokku report
. The version should be there. Running dokku-update run --skip-rebuild
will update dokku and all of it's dependencies, including herokuish.
thanks @josegonzalez, dokku report
give me this after running dokku-update run --skip-rebuild
. However Herokuish seems to be locked at version 0.7.2.
Errors are still there.
dokku report
...
-----> herokuish version:
herokuish: v0.7.2
buildpacks:
heroku-buildpack-multi v1.2.0
heroku-buildpack-ruby v259
heroku-buildpack-nodejs v224
heroku-buildpack-clojure v91
heroku-buildpack-python v237
heroku-buildpack-java v73
heroku-buildpack-gradle v39
heroku-buildpack-scala v96
heroku-buildpack-play v26
heroku-buildpack-php v239
heroku-buildpack-go v181
heroku-buildpack-nginx v24
buildpack-null v3
-----> dokku version: dokku version 0.34.3
! dokku-event-listener binary is not available
-----> dokku-update version: dokku-update 0.8.0
-----> docker-container-healthchecker version: 0.9.0
-----> docker-image-labeler version: 0.6.1build+c6e15a9
...
-----> dokku plugins:
00_dokku-standard 0.34.3 enabled dokku core standard plugin
20_events 0.34.3 enabled dokku core events logging plugin
...
builder-herokuish 0.34.3 enabled dokku core builder-herokuish plugin
...
Can you verify that you haven't somehow pinned herokuish? Potentially you are managing that server with our ansible modules and you need to update it there, since we pin versions in the ansible modules.
If you aren't, then you might have a file in /etc/apt/preferences.d
that pins herokuish to an older version.
So for me it worked! did update with dokku-update run and it updated dokku and herokuish and also it seems I can now push my apps again! Thanks for the fix!
thanks, I have just to install herokuish manually (apt install herokuish
) and run dokku-update
and it works now!
Description of problem
I recently updated to the latest dokku (0.34.2) and am now running into an issue that when I deploy an app that uses a storage i get an error that looks like this:
I tried to change the ownership of that folder under /var/lib/dokku/data/storage/personal-cms but that did not help. Havent had the problem before I updated, but also I dont now which version I was on previoulsy.
Steps to reproduce
adding a storage to an app, put the app.
dokku report $APP_NAME
Additional information
No response
Output of failing commands after running: dokku trace:off
No response
Output of failing commands after running: dokku trace:on
No response