How to enable Husarnet Hooks in a Docker Image?

[ralves]

Hi,

I’ve been following the tutorial about Husarnet Hooks but what I’m really trying to do is to have a Docker Image with Husarnet installed and the hooks enabled (not enabling on the host, but inside a Docker Image).

I know there is already a Husarnet Docker Image (husarnet/husarnet:latest), so I just used it as a base.

The current Dockerfile I have is this one:

FROM husarnet/husarnet:latest

ENV RELEASE="v1.3.6"
ENV ARCH="amd64"

SHELL [ "/bin/bash", "-c" ]
RUN mkdir -pv /usr/local/bin/
ADD https://github.com/husarnet/husarnet-dds/releases/download/$RELEASE/husarnet-dds-linux-$ARCH /usr/local/bin/husarnet-dds

RUN chmod +x /usr/local/bin/husarnet-dds \
    && mkdir -pv /var/lib/husarnet/hook.whitelist_changed.d \
    && touch /var/lib/husarnet/hook.whitelist_changed.d/dds-update.sh \
    && echo -e '#!/bin/bash \n\n husarnet-dds singleshot' | tee /var/lib/husarnet/hook.whitelist_changed.d/dds-update.sh \
    && chmod +x /var/lib/husarnet/hook.whitelist_changed.d/dds-update.sh

# RUN husarnet & husarnet daemon hooks enable
RUN husarnet daemon hooks enable

And I try to create image like this:

docker build -t husarnt_with_hooks:husarnet .

But it doesn’t work because we don’t have Husarnet Daemon running.

Do you have any way of making the hooks be enabled in a Docker Image?

I thought that there could be a single config file where we could enable or disable the hook, but when testing on my local pc (not inside the docker), I checked the content of /var/lib/husarnet/ before and after enabling the hook but I couldn’t see any changes in this folder or in the license.json file.

So my question is:

• Is it possible to enable the hooks in a Docker Image?

[pidpawel]

Hi!
I have not tested it yet, but I think the easiest way of enabling hooks from Dockerfile would be to make it save

{
    "user-settings": {
        "enableHooks": "true"
    }
}

as /var/lib/husarnet/config.json - instead of RUN husarnet daemon hooks enable
This essentially is what makes the daemon start with hooks enabled. Out of curiosity (as we’re changing some things when it comes to hooks right now) what’s your planned usecase for hooks and what signals would be helpful in the future?

–
Have a wonderful day
Paweł

[ralves]

Hi @pidpawel,

Thanks for the instructions on how to manually enable hooks on the config.json file.

About my usecases, I basically work with Ricardo on The Construct and we provide a rrl-setup.sh that users run on their system to install Husarnet on their host, but we want to try Docker instead. We currently have a script that watches for /etc/hosts changes and updates the DDS XML files when /etc/hosts changes, but I thought of using your husarnet-dds solution.

[dominik]

Hi @ralves , husarnet-dds is only one of available methods. We have listed and described different options in this article: Using Husarnet & ROS 2 | Husarnet

[ralves]

Hi @pidpawel and @dominik,

Just to let you know, I noticed that sometimes (not consistently) when I click on the “Refresh device status” in a network page (like https://app.husarnet.com/network/13031, for example) to get the robot status, my robot (my PC actually) disconnects and I can see this message on Husarnet logs:

2025-02-21_01:53:29 CRITICAL unhandled exception in thread websetupConnection: [json.exception.type_error.302] type must be boolean, but is string

This happened many times while I was doing some tests today in other networks that I already removed (I think I removed networks with the IDs 13018 and 13030).

As I mentioned, it doesn’t happen always, but it happened many times while I was doing some tests.