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: open
Created a year ago
Reactions: 2
Comments: 18 (8 by maintainers)

Most upvoted comments

Is there an upgrade path from v3 to v4 yet?

There will be, but not with a simple button. 🙂

andrasbacsai on Jul 7, 2023

is there an upgrade path from v3 to v4 yet?

It’s not worth upgrading yet since there is still a lot missing.

ikbenignace on Jul 6, 2023

I ran into 2 issues when installing beta 4.00-18

apparently, the database crashes at the start and is stuck in a infinite restart loop
can’t connect to the web ui ,the web UI is port forwarded from 3000 - >5000 but the URL generated by the bash script says its on port 8000

environment:

digital ocean droplet:

2 cpu
4 gb ram
80 gb storage
ubuntu 22.04

root@ubuntu-coolify-test:~# 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: ubuntu 22.04
Coolify version: 4.0.0-beta.18
-------------
Installing required packages...
-------------
Check Docker Configuration...
Docker configuration is up to date.
-------------
Downloading required files from CDN...
latest: Pulling from coollabsio/coolify-helper
Digest: sha256:bf5b666b107229a21912ae667a365af8af5dcb75eedc751b29f87cb97624c834
Status: Image is up to date for ghcr.io/coollabsio/coolify-helper:latest
 redis Pulling 
 coolify Pulling 
 postgres Pulling 
 coolify Pulled 
 redis Pulled 
 postgres Pulled 
time="2023-08-12T16:27:56Z" level=warning msg="volume \"coolify-db\" already exists but was not created for project \"app\". Use `external: true` to use an existing volume"
 Container coolify-redis  Recreate
 Container coolify-db  Recreate
 Container coolify-db  Recreated
 Container coolify-redis  Recreated
 Container coolify  Recreate
 Container coolify  Recreated
 Container coolify-db  Starting
 Container coolify-redis  Starting
 Container coolify-db  Started
 Container coolify-redis  Started
 Container coolify-redis  Waiting
 Container coolify-db  Waiting
 Container coolify-db  Error
 Container coolify-redis  Healthy
dependency failed to start: container coolify-db is unhealthy

Congratulations! Your Coolify instance is ready to use.

Please visit http://xxx.xxx.xxx.xxx:8000 to get started.
root@ubuntu-coolify-test:~# docker ps
CONTAINER ID   IMAGE                               COMMAND                  CREATED          STATUS                         PORTS                                       NAMES
f97c7426178c   postgres:15-alpine                  "docker-entrypoint.s…"   15 seconds ago   Restarting (1) 4 seconds ago                                               coolify-db
9a1f3d0c9394   redis:alpine                        "docker-entrypoint.s…"   15 seconds ago   Up 13 seconds (healthy)        6379/tcp                                    coolify-redis
b93364c5f752   cll85tqx70002mjado2gqbtti:51d625a   "docker-entrypoint.s…"   55 minutes ago   Up 5 minutes                   0.0.0.0:5000->3000/tcp, :::5000->3000/tcp   cll85tqx70002mjado2gqbtti

@andrasbacsai

poipiii on Aug 12, 2023

I also got an error:

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.04
Coolify version: 4.0.0-beta.14
-------------
Installing required packages...
-------------
Check Docker Configuration...
Docker configuration is up to date.
-------------
Downloading required files from CDN...
latest: Pulling from coollabsio/coolify-builder
Digest: sha256:f2d783d5660e709a9001c53167ea9404e1db8314aab9483875773771a32091c3
Status: Image is up to date for ghcr.io/coollabsio/coolify-builder:latest
redis Pulling
coolify Pulling
postgres Pulling
redis Pulled
postgres Pulled
coolify Pulled
Network coolify  Creating
Network coolify  Created
Volume "coolify-db"  Creating
Volume "coolify-db"  Created
Volume "coolify-redis"  Creating
Volume "coolify-redis"  Created
Container coolify-redis  Creating
Container coolify-db  Creating
Container coolify-redis  Created
Container coolify-db  Created
Container coolify  Creating
Container coolify  Created
Container coolify-db  Starting
Container coolify-redis  Starting
Container coolify-db  Started
Container coolify-redis  Started
Container coolify-db  Waiting
Container coolify-redis  Waiting
Container coolify-db  Healthy
Container coolify-redis  Healthy
Container coolify  Starting
Error response from daemon: driver failed programming external connectivity on endpoint coolify (452ca7ce63deadf837a695583c5f5369d14278f608c1686bbcf1cdf47111b656): Bind for 0.0.0.0:8000 failed: port is already allocated

Congratulations! Your Coolify instance is ready to use.

(I took out my ip)

I already ran these commands to unallocated them butttttt. Its still not working.

sudo lsof -i :8000
sudo kill <PID>
sudo lsof -i :8000

That command showed that everything was working soooooooo.

It is because something is already running on port 8000. I will add a check in the installation script!

andrasbacsai on Jun 28, 2023

@andrasbacsai I believe the problem was curl -fsSL https://cdn.coollabs.io/coolify/install.sh | bash pointed to 4.0.0-beta.15 which didn’t exist in the packages until 4 hours ago meaning you had to use -s next to actually use 4.0.0-beta.15.

letto4135 on Jul 4, 2023