Bootstrap failed with exit code 128

Hi,

my old container still works, but i’m having trouble rebuilding. The same error appeared on both attempts before and after updating the ubuntu kernel by apt upgrade

regardless of the implementation of this

after getting fast data: to URL on safari PWA i ran reboot

so to get back to old container, with the web UI update interface not working unless a rebuild is successful

I think you need to add swap.

I have over 100GB of SSD space available- how do i officially allocate swap?

what does free -h return?

Swap uses some of your SSD as (very slow) RAM.

      install -o root -g root -m 0600 /dev/null /swapfile
      fallocate -l 2G /swapfile
      mkswap /swapfile
      swapon /swapfile
      echo "/swapfile       swap    swap    auto      0       0" | tee -a /etc/fstab
      sysctl -w vm.swappiness=10
      echo 'vm.swappiness = 10' > /etc/sysctl.d/30-discourse-swap.conf

what directory do i run these 7 commands in?

Any directory.

WIth 8GB you shouldn’t need swap, but it can’t hurt.

What error do you get when you rebuild?

That’s an example of why copy/paste is so helpful. You missed a / before your swapfile in the fallocate command.

1 Like

yes i did get PuTTy going but i found it glitchy sometimes with the highlighting

did it run ok

i do recall when first setting up the server on a contract with Ionos, their image of 22.04 Ubuntu didn’t work with .\discourse-setup so i had to modify the app.yml myself.

This was without Plesk, the Ionos data center designer self-image worked fine with .\discourse-setup beforehand

So this was a standard install and you created the app.yml with discourse-setup?

What error do you get when you rebuild?

1 Like

Well, I needed. Perhaps a giga would be enough, but I gave 2 GB.

2 Likes

yes i installed docker through .\discourse-setup

i’ll reply here if i get a rebuild error after setting up the swap