Gladys on windows 10

Hello. New to this, I am implementing Gladys on my MS surface with windows 10. so far i have:

  1. implemented virtual machines
  2. installed WSL - windows file explorer shows a Linux penguin.
  3. installed docker desktop for windows and selected the personal option.
  4. created a gladys image and a container where it runs. I can access this via localhost:8080

I am trying to implement the airzone cloud integration which i find in Gladys under integrations-heating. The instalation button fails « There was an error installing this integration. »

Google told me i needed to update the docker settings and enable integration with the default WSL distro. Initially there were none. So i have installed Debian and selected the distro. Debian now shows in windows file explorer next to docker-desktop within Linux. The integration error remains.

It looks like the problem is with access to the docker daemon and i imagine this may be to do with the path to the docker files or access privilidge (since i selected a personal implementation of Docker).

Running docker desktop as an administrator changes nothing. Ive pasted the error log below.

Evidently Ive done something wrong with the installation. Do I need to install docker desktop with the all users option? Or install docker in debian? Or install docker compose?

2026-10-29 12:16:58

Gladys_Main

2026-10-29T11:16:58+0000 <warn> errorMiddleware.js:83 (errorMiddleware) PlatformNotCompatible \[Error\]: SYSTEM_NOT_RUNNING_DOCKER

2026-10-29T11:16:58+0000 <warn> errorMiddleware.js:83 (errorMiddleware) PlatformNotCompatible \[Error\]: SYSTEM_NOT_RUNNING_DOCKER

2026-10-29 12:16:58

Gladys_Main

at ExternalIntegration.install (/src/server/lib/external-integration/externalIntegration.install.js:29:11)

    at ExternalIntegration.install (/src/server/lib/external-integration/externalIntegration.install.js:29:11)

2026-10-29 12:16:58

Gladys_Main

at ExternalIntegration.installFromStore (/src/server/lib/external-integration/store/store.installFromStore.js:20:15)

    at ExternalIntegration.installFromStore (/src/server/lib/external-integration/store/store.installFromStore.js:20:15)

2026-10-29 12:16:58

Gladys_Main

at install (/src/server/api/controllers/externalIntegration.controller.js:246:21)

    at install (/src/server/api/controllers/externalIntegration.controller.js:246:21)

Welcome @tameer!

I’m not a Windows expert but I can guide you, well I’ll try.
Personally, I wouldn’t take the Docker solution in Windows.
Apparently you can set up VMs so we’ll go through that.
I don’t know if you use Virtualbox or another, but I think the process is the same.

  • create the VM with Debian server or Ubuntu server, this VM must have a network access Bridge to get an IP from your network
  • install Docker in your VM
  • install Gladys: personally I prefer to use Docker Compose (easier to modify later if needed I find) but if it’s just for testing you can use the Docker run command from the documentation
  • connect to Gladys, normally it’s: http://gladysassistant.lan:8080 or http://VM-ip:8080

Keep us updated on your progress :slight_smile:

Thanks for the quick reply. I am confused because the latest main gladys-assistant image appears to run ok in docker desktop on WSL even without a full linux distribution.

For adding the airzone integration, the problem seems to be with not finding a dockerfile. The sample docker application « welcome to docker » sits in my user directory C:/users. But the gladys installed instance isnt shown there. I asked the Gordon AI where it is. It says "The application’s running image is gladysassistant/gladys:latest, and their current directory is empty, meaning the Dockerfile isn’t there." It thinks it might be in Github.

But surely in order to run locally, The gladys image should be somewhere on my machine with its associated dockerfile. Could it be hidden?

Maybe somewhere in %appdata% but I think you’ll spend a lot of time there… for me a VM and that’s it.

I have reinstalled with Ubuntu and docker descktop in « all user » mode which puts Docker under program files in the windows hierarchy. Docker settings modified to have integration with Ubuntu and to use WSL.

In the docker GUI, the gladys image loads into a new container without a host path or container path being specified in « optional settings ». If i knew what to specify, I could enter the path required.

The log shows: 2026-10-31T11:09:49+0000 system.isDocker.js:13 (System.isDocker) System.isDocker: This system is running inside Docker.

But the log also shows: 2026-10-31T11:09:23+0000 externalIntegration.init.js:62 (ExternalIntegration.init) External integrations are not available: Gladys has no access to a Docker socket!

So this is what i need to resolve. Is it a path problem or a privilige problem? What to try next?

I have been wondering if my problem is because i have been pulling and running gladys with the GUI rather than the command line. So i have tried the script from:" Install Gladys with Docker on Debian, Ubuntu & more | Gladys Assistant " using powershell. I see the line « –privileged \ » which could be what i am missing with the GUI.

The container shows in the GUI without an access link and i cant access gladys from my browser using "http://gladysassistant.local" . The ip addresses i find in ipconfig dont work either

So the new gladys might be able to access the Daemon but I need to be able to access gladys in the browswer to find out! :frowning:

Ethernet adapter Ethernet 4:

Connection-specific DNS Suffix . : Tameer-Subnet
IPv6 Address. . . . . . . . . . . : fd0b:5995:6fcf::8d7
Link-local IPv6 Address . . . . . : fe80::367a:e704:5db0:dfb2%27
IPv4 Address. . . . . . . . . . . : 192.168.0.34
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1

Ethernet adapter Bluetooth Network Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Ethernet adapter vEthernet (Default Switch):

Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::5e3:668b:b860:3740%21
IPv4 Address. . . . . . . . . . . : 172.17.208.1
Subnet Mask . . . . . . . . . . . : 255.255.240.0
Default Gateway . . . . . . . . . :

Ethernet adapter vEthernet (WSL):

Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::e5a5:d01:fde5:8fce%41
IPv4 Address. . . . . . . . . . . : 172.24.96.1
Subnet Mask . . . . . . . . . . . : 255.255.240.0
Default Gateway . . . . . . . . . :

Hi,
Gladys needs access to the Docker socket, so the container has to be started with /var/run/docker.sock mounted, and with host networking. Docker Desktop on Windows is limited on both points, which probably explains the SYSTEM_NOT_RUNNING_DOCKER message.
A small Linux VM or a Raspberry Pi is usually much simpler for this.

Thanks for that explanation. I will need to use a script then.

I have returned this evening to find a power problem and the ms surface wont start. It may be just a deep battery discharge but if not i may need to buy a new mini pc - or a home assistant green.

Will report progress tomorrow.

I have abandoned the docker desktop GUI apart fom setting the options to staryt the docker engine when i log on to the pc, running containers on WSL 2, and WSL integration with Ubuntu in the resources tab.

And to help setup networking and privilidge correctly, i have gone for docker compose (which is installed as part of the docker descktop installation. I have copied the script from Install Gladys Assistant with Docker Compose | Gladys Assistant and created the .yml file. The tutorial says store in a directory on your system which is a bit vague. I created a gladys directory under my user directory which seemed logical.

I had to be very specific with the path to activate the script! Otherwise it isnt found.
tameer@SURFACE-3-JBS:/mnt/c/Users/Tameer$ ls gladys
gladys-compose.yml
tameer@SURFACE-3-JBS:/mnt/c/Users/Tameer$ sudo docker compose -f gladys-compose.yml up -d
compose file « /mnt/c/Users/Tameer/gladys-compose.yml » is invalid: open /mnt/c/Users/Tameer/gladys-compose.yml: no such file or directory
tameer@SURFACE-3-JBS:/mnt/c/Users/Tameer$ sudo docker compose -f ./gladys/gladys-compose.yml up -d
[+] up 11/11
:check_mark: Image gladysassistant/gladys:v5 Pulled 2.4s
:check_mark: Image nickfedor/watchtower Pulled 8.4s
:check_mark: Network gladys_default Created 0.5s
:check_mark: Container gladys Started 5.3s
:check_mark: Container watchtower Started 4.3s
tameer@SURFACE-3-JBS:/mnt/c/Users/Tameer$

As before gladysassistant.local does not open. i still dont know which ip address is needed but localhost/gladysassistant.local did work. Hurray!

Sadly the airzone integration will still not install correctly from gladys. « There was an error installing this integration. » Can the integration be added to the yml file or installed directly from the command line?

The airzone integration seems to be running in some way:
tameer@SURFACE-3-JBS:/mnt/c/Users/Tameer$ docker ps

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
169fcf74ad2b Package gladys-airzone-cloud · GitHub « dumb-init – node i… » 5 minutes ago Up 5 minutes gladys-ext-callemand-gladys-airzone-cloud
37e5848904d0 nickfedor/watchtower « /watchtower --clean… » 27 minutes ago Up 27 minutes (healthy) 8080/tcp watchtower
208946c22467 gladysassistant/gladys:v5 « docker-entrypoint.s… » 27 minutes ago Up 27 minutes gladys

something to do with « dumb-init » ?

Why don’t you just uninstall Windows 10 or create a VM and in both cases directly install the new all-in-one image? https://community.gladysassistant.com/t/gladys-assistant-os-installez-gladys-sur-un-mini-pc-avec-une-simple-cle-usb/

This seems like a much more obvious solution because even with a VM, if you need specific USB ports or folders, etc., it will cause you trouble…

Yes I could just replace windows with ubuntu. But I have windows apps on the pc that i cant transfer. alors j’esseye de me demerder. When i have established proof of concept, i may then buy a mini pc. For now my surface 3 pro is free. And since gladys is supposed to run on any docker, I’m pursuing the option.

Progress! despite saying the integration failed, gladys ran the airzone integration and let me enter my airzone cloud credentials. Slight complication - the airzone cloud app was updated last night and now requires a subscription. So i have signed up for the 6 month free trial and I can now see my heating zones in gladys! Phew!

Now i am trying to see if i can control the heating zones in Gladys.