avahi | Service Discovery for Linux using mDNS | DNS library

Is there an elegant way to convert "test\207\128" into "testπ" in python?

My issue stems from using avahi-browse on Linux, which has a -p flag to output information in an easy to parse format. However the problem is that it outputs non alpha-numeric characters as escaped sequences. So a service published as "name#id" gets output by avahi-browse as "name\035id". This can be dealt with by splitting on the \, dropping a leading zero and using chr(35) to recover the #. This solution breaks on multi-byte utf characters such as "π" which gets output as "\207\128".

I am creating a script that takes a group name, and it should print all the users and the groups they are in including the given one, but I still can't figure out how to do it properly, here is my code:

I have a single board computer running. (1GByte - RAM) I started 11 different Docker containers via a Docker compose file and this worked! To be clear. I can docker-compose down - docker-compose up at any time. No Problem.

This is the docker stats for overview names replaced with xxx

I have a problem and I don't know where to look for the problem. I'm running debian:buster and I'm trying to set it up as a jellyfin server.

I added the nessecary architecture (amd64).

Trying to set up a network printer with CUPS.

Followed online documentation that stated:

To discover or share printers using DNS-SD/mDNS, setup .local hostname resolution with Avahi and restart cups.service.

Followed directions for setting up Avahi to the point where avahi-browse --all --ignore-local --resolve --terminate and avahi-resolve-host-name my-domain.local are both working.

But getent hosts my-domain.local fails to resolve. This results in CUPS failing to print because it can't find my-printer.local.

I have heard its a conventional practice to store program dependent files in /usr/share/application-folder in linux. So I'm trying to do it in my c program in a function called load_interface_files() for example. I am not sure if this is a good practice or not, I've heard about creating configuration files for this kind of issues.

Anyways, here's the the code I wrote to make a directory in /usr/share.

I am trying to resolve IPv4 and IpV6 from ".local" using multicast DNS and I tried https://github.com/posicks/mdnsjava but it unable to resolve required ipv4/ipv6. Alternatively, I found one app which work for me but have no idea how it works.

App Link : https://play.google.com/store/apps/details?id=com.dokoden.dotlocalfinder

Also I am trying to resolve ".local" using Linux Terminal -
Command used to resolve ipv4 avahi-resolve-host-name abc.local -4
Command used to resolve ipv6 avahi-resolve-host-name abc.local -6
and it resolved successfully.

I am tried same command in Android to resolve ".local" but getting Cannot run program "avahi-resolve-host-name": error=13, Permission denied

I am trying this piece of code in Android -

I'm using a Raspberry Pi 4 Model B and i want to run the Openthread Border Router application on it as a docker container. I use the command docker run --sysctl "net.ipv6.conf.all.disable_ipv6=0 net.ipv4.conf.all.forwarding=1 net.ipv6.conf.all.forwarding=1" -p 8080:80 --dns=127.0.0.1 -dit --network test-driver-net --volume /dev/ttyACM0:/dev/ttyACM0 --name ot-br --privileged openthread/otbr --radio-url spinel+hdlc+uart:///dev/ttyACM0 to start the container. I have tried the openthread/otbr:latest and the openthread/otbr:reference-device (both pushed 10. Nov. 2020) image, both were having the same problem:

The container is started successfully, but the Web-GUI is not available and no network operation takes place. Here is the logged output of the containers if called upon with docker logs ot-br:

Why does the following cut out the word root on the second line and skew the output, not to be uniform to all the following lines?