What this lsmod | grep kvm returns?
Errors when installing appwrite (Ubuntu Server 22.04 64 Bit)
Votes
1
Replies
24
Participants
Unknown
Messages
25
Rank 2: Process
You something that limit your server
Do running ulimit -s unlimited and then docker compose up -d makes any different?
Rank 2: Process
i saw that some process and storage limit is enabled by default in the server console and i disabled that after i resetted the server before
Rank 2: Process
now after ulimit -s unlimited and docker compose up -d still the same error:
Okay, I think a good approach to tackle it would be to try to run the docker-compose.yml services one by one to find the problematic one.
docker compose run -d mariadbdocker compose run -d redisdocker compose run -d influxdbdocker compose run -d telegrafdocker compose run -d appwritedocker compose run -d traefikdocker compose run -d appwrite-executordocker compose run -d appwrite-realtimedocker compose run -d appwrite-worker-auditsdocker compose run -d appwrite-worker-webhooksdocker compose run -d appwrite-worker-deletesdocker compose run -d appwrite-worker-databasesdocker compose run -d appwrite-worker-buildsdocker compose run -d appwrite-worker-certificatesdocker compose run -d appwrite-worker-functionsdocker compose run -d appwrite-worker-mailsdocker compose run -d appwrite-worker-messagingdocker compose run -d appwrite-maintenancedocker compose run -d appwrite-usagedocker compose run -d appwrite-scheduleIn this order
Rank 2: Process
@Binyamin those are the containers that fail when trying to run them: audits, certificates, mails, messaging, maintenance, usage, schedule
Any one of them product the same error above?
Rank 2: Process
yes, all with the same error. Its Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error running hook #0: error running hook: exit status 2, stdout: , stderr: runtime/cgo: pthread_create failed: Resource temporarily unavailable and the audits one has produced Error response from daemon: failed to start shim: start failed: runtime: failed to create new OS thread (have 2 already; errno=11) runtime: may need to increase max user processes (ulimit -u)
It's interesting did you installed go?
Let's try one last thing
Reset the server and try all the steps in this link
https://discord.com/channels/564160730845151244/1097119647867863090/1097199871624228934
Including the docker installation via the .sh file
Admin
it really could be an OS level system limit like this error says. maybe you have some non-standard ubuntu installation
I agree
Rank 2: Process
i will do that! I am probably not able to do thay today but ill complete these steps tomorrow and then give a feedback here. Thanks so far for your help guys, you are awesome!
But it's seems a bit wired that clean Ubuntu 22 will produce this kind of errors
Rank 2: Process
yeah i also think that. It feels like that the provider i choose is pretty bad 😅
Rank 2: Process
i cannot really tell if its clean because i cannot upload an iso myself. there is a predefined list of operating systems
What company it is?
Rank 2: Process
strato.de
Most of the time they will give you near-clean installation
Rank 2: Process
their web panel is also quite cursed. In their docs there are infos about how to setup firewall rules but there is no option to do that when logging in. I cannot even restart or stop the server. To do that i have to switch to "Recovery Mode" and back to "Production mode". That seems like a pretty bad admin console to me😕
I would recommend you either Linode or Digital ocean or Vultr
All of them have servers in Germany.
Rank 2: Process
i will check them out, thanks! Strato is quite cheap. That should have been a warning to me before. Currently i pay 6€/6$ per month for 4 CPU cores, 8GB, 300GB
It's pretty cheap, But maybe it means that you're part of bigger system and 100% isolated VPS.
Rank 2: Process
Ok guys thank you so much for your work, i really appreciate it! I will try to reset the server and install appwrite manually tomorrow and post the results here. If its not working it has to be a OS error