-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
24.4.2 - OCI runtime create failed: runc create failed #3023
Comments
@azaslavsky - one approach there is to run "./reset.sh" which is no option as we need the captured Data. The other one is to chmod 777 everything - doesn't sound like an approach one wants to do on a productive machine?
Also on both of those 2 linked issues it's failing on postgres which in this case isn't the problem if I don't overlook anything?
Any other ideas on how to further debug this issue? |
Some googling revealed this suggestion, but tat this point I am just prowling the internet for random answers. This error is very likely to do with your system configuration - in the past, this has often been with regards to permissioning, hence why |
@azaslavsky unfortunately the max_user_namespaces also seems to be already high enough here:
I'm running Sentry on clean install of AlmaLinux 8:
running out of ideas on what else to try to get sentry updated here :-( |
I'm not sure what we can do remotely either. We test on ubuntu and alpine linux, and it works in both environments. Ultimately, there are any number of reasons why this could pop up, and the solution is likely not self-hosted specific. |
Hey @futureweb can you try to install it on higher version of AlmaLinux? A wild guess from me is that it failed to build on Linux kernel 4.x, but AlmaLinux 9.x and Ubuntu 20.x uses Linux kernel 5.x. If you're okay with moving to some other distro other than RHEL derivatives, I'd highly recommend to install sentry self-hosted on Debian 12. If installing on AlmaLinux 9.x or Debian 11/12 works with no problem, then I can assume that.. Docker does not plays well with old distro running old kernel version. |
@aldy505 - as we operate all our Servers on RHEL based Servers we would like to stay within this universe, if possible.
seems like no luck with rhel based servers here?!? :-( |
update: after running /var/www/sentry/self-hosted/scripts/reset.sh and another fresh install the installation went through completely ... but then when I tried to fire it up:
damnit ... this is frustrating :-( |
further update:
Then the Will try to see if I can migrate old Data to new Server + then Update to latest Sentry |
I wonder if you could actually try Debian or Ubuntu just for the sake of it, and see if it suddenly works..... |
@aldy505 never worked with Debian so far - but yea - could create a Debian Machine and try. I guess it should work there when it's tested on Debian ^^ |
Self-Hosted Version
24.4.2
CPU Architecture
x86_64
Docker Version
Docker version 26.1.1, build 4cf5afa
Docker Compose Version
Docker Compose version v2.27.0
Steps to Reproduce
Update or fresh Re-Install Version 24.4.2 (coming from Sentry 23.7.2 adbbcd8)
Fire it up (docker compose up -d)
Won't start - Error:
Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: can't get final child's PID from pipe: EOF: unknown
Expected Result
Sentry should start without Problems
Actual Result
composer.log
install.log
Event ID
No response
The text was updated successfully, but these errors were encountered: