Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ERROR: for nubo-frontend Cannot start service nubo-frontend #1

Open
assasen11 opened this issue Dec 30, 2021 · 1 comment
Open

ERROR: for nubo-frontend Cannot start service nubo-frontend #1

assasen11 opened this issue Dec 30, 2021 · 1 comment

Comments

@assasen11
Copy link

assasen11 commented Dec 30, 2021

I am not in dire need for this to work I had just wanted to test it. I figured I would share my issues encase its a broad one and can do further testing on different versions.

I am running AlmaLinux release 8.5 (Arctic Sphynx)

I followed the instructions to just copy and paste the curl script.

I am getting an already in use error when it tries to run through the script

`nubo-management is up-to-date
Creating nubo-frontend ...
Host is already in use by another container
Creating nubo-frontend ... error

ERROR: for nubo-frontend  Cannot start service nubo-frontend: driver failed programming external connectivity on endpoint nubo-frontend (54e10670acebf1edf8414fb85ed3e9b5e45d692a3b4dd0ebe043a8cdb10c7ad6): Error starting userland proxy: listen tcp4 0.0.0.0:443: bind: address already in use
Creating nubo-ps       ... done
Creating nubo-guac     ... done

ERROR: for nubo-frontend  Cannot start service nubo-frontend: driver failed programming external connectivity on endpoint nubo-frontend (54e10670acebf1edf8414fb85ed3e9b5e45d692a3b4dd0ebe043a8cdb10c7ad6): Error starting userland proxy: listen tcp4 0.0.0.0:443: bind: address already in use
Encountered errors while bringing up the project.
`

I also see a separate error a few lines up and am unsure if it is relevant.

`Configuring organization and user...
Starting all containers...
Error Error: Command failed: /usr/local/bin/docker-compose up -d
The MYSQL_PASSWORD variable is not set. Defaulting to a blank string.
`

When I check ss | grep 443 it shows

`@remote ~]$ ss | grep 443
u_str ESTAB  0      0      /run/containerd/s/0f09fb62a98fa9acb443ab08da637750f5dbc3de8c69af213598d7d486baf4b1 109912               * 109906
`

Now that container may be irreverent because it doesn't look like anything is even using port 443.

@nubosoftware
Copy link
Owner

Hi,

The frontend service is trying to bind port 443 which is already occupied by another process in the host machine.

You can change the listen port by editing /opt/nubo/docker-compose.yml

Steps:

  1. Run the bootstrap script again.
  2. When you see the first prompt message Ready to begin? [Y] , before clicking enter, go to another terminal window.
  3. Edit /opt/nubo/docker-compose.yml and change the following line: - "443:443" to map to another port in your host. e.g. for 8443 change it to - "8443:443" . Make sure to keep the indentation which is important in yml files. Save the file.
  4. Continue the bootstrap script by click enter.

You may need also to change port 80. You can do that by changing the - "80:80" line.

Please let me know if that solve this issue.

Best,
Nubo software

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants