Issue installing Gladys on Debian 10 with Docker

Configuration
1

Hello to the community,
After many hesitations, I decide to install Gladys, Docker installation under Debian 10 and Gladys in the process. I encounter a problem to start Gladys, I type the IP of my Gladys machine and it displays the screen indicating to me
This is the default home page used to test the proper functioning of the Apache2 server after installation on Debian systems. If you can read this page, it means that the HTTP Apache server installed on this site is working correctly. You must replace this file (located at /var/www/html/index.html) before continuing to use your HTTP server.
The default configuration of Apache2 of Debian is different from the default configuration upstream and divided into several optimized files for interaction with the Debian tools. The configuration system is fully documented in /usr/share/doc/apache2/README.Debian.gz. Refer to this for complete documentation. The documentation of the web server itself can be found by accessing the manual if the apache2-doc package has been installed on this server.
The layout of the configuration for an Apache2 web server installation on Debian systems is as follows:
/etc/apache2/
|-- apache2.conf
| -- ports.conf |-- enabled for mods | |-- *.load | – *.conf
|-- enabled conf
| -- *.conf |-- enabled for sites – *.conf

Can you help me before making a mistake or mistakes. Novice, thank you in advance.

2

Hello @lanews and cool if you’ve taken the plunge! :slight_smile:

Your version of Debian 10 should install Apache 2 by default, and thus Gladys should not be able to launch as port 80 is already in use..

Several options are available to you:

  • Uninstall Apache
  • Reinstall Debian with a version without Apache
  • Keep Apache but run Gladys on another port.

PS: I deleted your other message, I think it was a duplicate you posted the message twice?

3

Hello @pierre-gilles,
Why not consider running Gladys on a port other than 80 by default (Domoticz and Home Assistant are on other ports)? Are there technical reasons for this?

4

Simplicity is the default HTTP listening port.

5

Yes indeed I agree with @VonOx, for simplicity reasons :slight_smile:

After that, as you launch Gladys with Docker, the port is in the Docker run parameters that you use, you can change it very easily

6

Certainly, it would be better to be able to modify it easily in Gladys rather than having to tinker for that! It would be simpler for the « keyboard delicate Â» ones, right? :wink:

7

There’s no trick, you map the port you want, it’s standard Docker.

It’s in the docs => Installation avec Docker | Gladys Assistant

image

8

And when did we do the install on the Raspberry? I think it would be great to have it in the ‹ Settings â€ş section if it’s not a complicated development, but well!

9

The raspberry gladys image is already pre-configured, there is no port conflict.

To my knowledge, the foundation’s image does not have Apache installed by default.

This development is possible but time-consuming and adds little value, not to mention the risk factor as it requires destroying and recreating the container.

You can create a feature request without any problem → Demande de fonctionnalités - Gladys Assistant community

The requests with the most votes are developed

10

Ok it’s done :wink: After wait and see :grinning:

11

I agree with @VonOx, I don’t see the point of changing the port afterwards.

  • Either you are a beginner and you launch Gladys via a pre-configured image that is already set up with the right settings. In which case, you don’t even know what a port is, and you don’t need to worry about it. No consumer product talks about ports to its users.

  • Or you launch Gladys manually (it’s you who types the docker run command), in which case you can easily set the port adapted to your environment. If you made a mistake that causes a port conflict like here, being able to change the port in the interface won’t change anything because you don’t have access to the interface (Gladys doesn’t even start)

So for me the feature request doesn’t make sense, I think we can remove it ^^

12

Bon ok after installing docker on Ubuntu Linux Lite 5.6 Release 20.04 Codename: focal
I get this result when I try to install the Gladys container

docker run -d --log-opt max-size=10m --restart=always --privileged --network=host --name gladys -e NODE_ENV=production -e SERVER_PORT=8021 -e TZ=Europe/Paris -e SQLITE_FILE_PATH=/var/lib/gladysassistant/gladys-production.db -v /var/run/docker.sock:/var/run/docker.sock -v /var/lib/gladysassistant:/var/lib/gladysassistant -v /dev:/dev -v /run/udev:/run/udev:ro gladysassistant/gladys:v4
docker: Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Post "http://%2Fvar%2Frun%2Fdocker.sock/v1.24/containers/create?name=gladys": dial unix /var/run/docker.sock: connect: permission denied.
See 'docker run --help'

I’m stuck now! :roll_eyes:

13

It looks like you didn’t follow the Docker installation procedure; your user needs to be part of the docker group to have the correct permissions. By the way, you could have stayed on Debian; you just needed to uninstall Apache.

docker: Got permission denied

14

Bah I just had to be a brute :face_with_raised_eyebrow:…only do what is written! :innocent:
It was indeed missing (I am on a Beelink BT3 Pro NUC)

sudo usermod -aG docker $USER
newgrp docker

Now it works …on port 8021 as I wanted! Should add the link in the doc for the « no-vices Â»! :joy:
I can finally install NODE-RED and move forward with the connection to my IPX :stuck_out_tongue:
And Debian, well I’ll retest later because yesterday no terminal access after the install (apparently a loopback issue on the HDMI that would be fixed with an « dongle Â» HDMI)
Same with normal Ubuntu, it’s only with the Lite that it was OK at the same time I didn’t dig deeper into the matter…
Bonus: my super SONOFF Zigbee USB key on sale for €8.99 at domo is recognized!
Thanks anyway for the help :+1:

15

Great, the installation of node-red went smoothly by copying and pasting as in the documentation :+1:

Apart from that, at the end, it would be good to mention how to access it for those who don’t know. So to access it, it’s in the browser at http://gladys-ip:1880! :wink: