coolify: [Bug]: various v4 beta install issues
Installing 4.0.0-beta.12 on a fresh Ubuntu 22.10 VM.
Installation needs sudo su
Running the installation one-liner throws the error “Please run as root”, and running with sudo throws the same error. Needed to run sudo su to get it to work.
Issues installing docker
The first time the installation script completed, it seemed to fail installing Docker, but displayed a “completed” message anyway. Here’s what the terminal showed:
-------------
Welcome to Coolify v4 beta installer!
This script will install everything for you.
(Source code: https://github.com/coollabsio/coolify/blob/main/scripts/install.sh)
-------------
OS: ubuntu 22.10
Coolify version: 4.0.0-beta.12
-------------
Installing required packages...
Docker is not installed. Installing Docker...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 21734 100 21734 0 0 42065 0 --:--:-- --:--:-- --:--:-- 42120
# Executing docker install script, commit: a8a6b338bdfedd7ddefb96fe3e7fe7d4036d945a
+ sh -c apt-get update -qq >/dev/null
+ sh -c DEBIAN_FRONTEND=noninteractive apt-get install -y -qq apt-transport-https ca-certificates curl >/dev/null
E: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 3577 (unattended-upgr)
E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
Docker installed successfully
-------------
Check Docker Configuration...
jq: error: Could not open file /etc/docker/daemon.json.original-20230623-133634: No such file or directory
Docker configuration updated, restart docker daemon...
Failed to restart docker.service: Unit docker.service not found.
-------------
Downloading required files from CDN...
/data/coolify/source/upgrade.sh: line 18: docker: command not found
Congratulations! Your Coolify instance is ready to use.
Please visit http://77.175.38.180:8000 to get started.
Docker was not installed at this point. (I checked by running docker ps.)
However, I immediately ran the one-liner once more, and this time Docker was successfully installed, and the containers were running correctly.
IP vs Localhost
On my particular setup, http://x.x.x.x:8000 does not resolve in the browser, but localhost:8000 does. Perhaps both links can be displayed?
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 4
- Comments: 29 (9 by maintainers)
I ran into 2 issues when installing beta 4.00-18
environment:
digital ocean droplet:
@andrasbacsai
There will be, but not with a simple button. 🙂
It’s not worth upgrading yet since there is still a lot missing.
It is because something is already running on port 8000. I will add a check in the installation script!
Good news… I followed all the steps for uninstalling (https://coolify.io/docs/uninstall) and then it worked. Thanks!
root@fedora:/home/kumar# curl -fsSL https://cdn.coollabs.io/coolify/install.sh | bash
Welcome to Coolify v4 beta installer! This script will install everything for you. (Source code: https://github.com/coollabsio/coolify/blob/main/scripts/install.sh )
OS: fedora 40 Coolify version: 4.0.0-beta.297
Installing required packages… OpenSSH server is installed. PermitRootLogin is enabled.
Check Docker Configuration… Docker configuration is up to date.
Downloading required files from CDN… Container coolify-db Recreate Container coolify-realtime Recreate Container coolify-redis Recreate Container coolify-redis Recreated Container coolify-db Recreated Container coolify Recreate Container coolify Recreated Container coolify-realtime Recreated Container coolify-db Starting Container coolify-redis Starting Container coolify-realtime Starting Container coolify-db Started Container coolify-redis Started Container coolify-db Waiting Container coolify-redis Waiting Container coolify-realtime Started Container coolify-db Error Container coolify-redis Error dependency failed to start: container coolify-db is unhealthy
i do also get the same problem
I still have the same issue as @poipiii
@andrasbacsai Maybe I’m wrong but when piping the curl output to bash, it’s creating an unprivileged shell? It should be
curl -fsSL https://cdn.coollabs.io/coolify/install.sh | sudo bashI remember coolify v3 was like that.@andrasbacsai I believe the problem was
curl -fsSL https://cdn.coollabs.io/coolify/install.sh | bashpointed to 4.0.0-beta.15 which didn’t exist in the packages until 4 hours ago meaning you had to use-s nextto actually use 4.0.0-beta.15.