no such image error when installing

[STLawson]

This project looks really interesting, but I'm getting an error when trying to install.
When I go to run the start.sh file, I'm getting the following error:

ERROR: no such image: meienberger/runtipi:: invalid reference format
Failed to start containers

Any ideas on what I'm doing wrong? Looking into the images I have in docker, there's an unused "meienberger/runtipi:latest".

[meienberger]

Hello, this seems like you don’t have the version saved in you .env file.

1. Do you see TIPI_VERSION=0.6.0 When you do sudo cat .env
2. Are you running the start command from the runtipi folder ? If yes is there any error before no such image ?

[meienberger]

Another user encountered the same issue. The resolution was to install jq before running the start script. PR fixing this #171

[dibu28]

I have the same problem:

[meienberger]

I see the error in your console jq not found can you install it manually ? If you are running Debian or Ubuntu :
sudo apt install jq

[dibu28]

Thank you.
I have installed jq.
now I have the next error "the port 3000 is taken" while in description on min github page it is said that it will start on port 80 by default. I don't know why it is trieing to take 3000 port.

I've tried --port 7000 as in example but no luck it still tries to take port 3000

[dibu28]

[meienberger]

True, I didn't provide a way to change the dashboard port. 3000 is a mistake in my code and should only be used in development. I'll release 0.6.1 today which will fix that.
If you want to start it in the mean time you can either:

1. Find which app is using port 3000 on your server and stop it
2. Change the docker-compose.yml file at line 96 and remove the port binding :

ports:
      - 3000:3000

[dibu28]

Thank you!
I've changed port on another container.

The last problem I have is: I've logged in from ip address directly and now if I log in from domain(cloudflare) name I always see this sign up syart page and can't login. Is it saving somethere base url?

[dibu28]

Ok. --domain helped solve this. But now I can login using ip. But that's not a problem.

The problem is that then I've restarted the server I wasn't able to login until I've re run the start command again with --domin parameter.

[meienberger]

This is expected because when you setup a domain, the cookie policy will only allow you to login from the domain as a security purpose