{"id":36881,"date":"2026-10-23T07:26:03","date_gmt":"2026-10-23T14:26:03","guid":{"rendered":"https:\/\/www.podfeet.com\/blog\/?p=36881"},"modified":"2026-10-23T07:26:03","modified_gmt":"2026-10-23T14:26:03","slug":"blip-linux-synology","status":"publish","type":"post","link":"https:\/\/www.podfeet.com\/blog\/2026\/10\/blip-linux-synology\/","title":{"rendered":"Nobody Asked Me to Run Linux on My NAS, and Yet Here We Are"},"content":{"rendered":"

You know the phrase, “Just because you can<\/em> do something, that doesn’t mean you should<\/em>“? I think there needs to be another phrase, something like, “Just because you might be able to do something, you should try.”<\/p>\n

That’s the way I feel about the nearly two and a half hours I spent over the weekend trying to install an application on Linux in a really difficult environment. Let the record show that I didn’t need<\/em> to do this. But every step of the way, I really felt that success was right around the corner. I knew that my time could easily have been better spent, but I couldn’t stop myself from trying even when the level of effort became absurd.<\/p>\n

The Problem to Be Solved<\/h2>\n

In a desperate attempt to justify the time I spent, let me see if I can come up with a believable problem to be solved. I’m working on a ScreenCastsONLINE video tutorial that will include teaching how to use the menu bar app, Blip, from blip.net<\/a>. Blip, as I explained in my article from 2025, Fast Point-to-Point File Transfer with Blip<\/a> is an AirDrop-like application that works across macOS, iOS\/iPadOS, Android, and Windows. I noted in the article that Linux was “coming soon”, which is normally French for “Don’t hold your breath.”<\/p>\n

And yet, when I started working on a script for my tutorial, I discovered that Blip is now available on Linux! Even though the ScreenCastsONLINE audience is primarily Apple-biased, I knew that if I could demonstrate how even Linux gets to play, it would cement the concept that Blip is truly cross-platform.<\/p>\n

I put out the call for help in the Podfeet Slack podfeet.com\/slack<\/a> in hopes of finding someone running Linux who could help me demonstrate the experience. The awesome and delightful Eddie Tonkoi said he’d be glad to help. The only problem is that we are 14 time zones apart, so creating a video of both sides at the same time would be impossible.<\/p>\n

Eddie did end up making the final video for the tutorial by recording on his end, but let’s not muddy up the story with the relatively simple solution, shall we?<\/p>\n

Linux on Synology<\/h2>\n

The story starts at 1:45 PM where I had a few hours to myself during naptime of the grandchild I was managing in Texas.<\/p>\n

I don’t have a Linux box, nor do I have an old machine that could be repurposed for the task. What I do have is a Synology at home. I can see the Synology desktop from a web browser like Safari on my Mac due to the magic of Tailscale. So we have a Mac using Tailscale to open a web browser to view the Synology.<\/p>\n

On a Synology, you can create Docker containers. I won’t go into the full, technical explanation of Docker containers, but it’s ok to think of them as being sort of like virtual machines with significant benefits.<\/p>\n

If you want to understand how they’re different and why they’re cooler, I highly recommend you take a read and\/or listen to Helma van der Linden explain the advantages of Docker containers in Programming By Stealth Tidbit 17<\/a>. For this exercise, you only need to know that Docker containers can provide a full operating system, such as Linux.<\/p>\n

Ok, my goal is then to have a Mac running Safari viewing the desktop of a Synology over Tailscale running a Docker container running Linux. The final step would be to install Blip.<\/p>\n

To summarize again, I want Blip running on Linux running in a container running on a Synology being viewed in Safari via Tailscale on macOS. Should be simple, right?<\/p>\n

\"iagram
Looks Easy, Right?<\/figcaption><\/figure>\n

Installing a Linux Container on Synology<\/h2>\n

I know my way around the Container Manager app on Synology’s DiskStation Manager (DSM), so I knew where to start. If you’re a super geek like Helma (or learned from Helma), you know how to build your own Docker containers. But if you’re a bit less nerdy, you can use the Registry tab to look for pre-built images, which will then build the Docker container.<\/p>\n

\"Container
Container Manager in Synology Disk Station Manager<\/figcaption><\/figure>\n

I asked my able assistant, Siri AI, for a recommendation of a “nice and light” version of Linux, and it suggested Alpine Linux. I succeeded with the installation inside the Docker container, but when they say “light”, they mean really light. Remember how we used to joke about how Spirit Airlines kept the prices low because you have to pay extra for a seat? Alpine is like that.<\/p>\n

\"Alpine
Alpine Linux is Definitely Light<\/figcaption><\/figure>\n

There wasn’t even an applications folder! I finally discovered that by right-clicking on the desktop, I could launch Terminal, but that was it. Time to abandon that<\/em> whole path!<\/p>\n

I downloaded the image again for linuxserver\/webtop, and this time asked for a version of Ubuntu. That sounded pretty mainstream.<\/p>\n

But get this. In the middle of following Siri AI’s instructions on how to install the Ubuntu container on my Synology, Siri AI ended the conversation<\/em>! Say what??? You don’t get to just leave<\/em>. Were you bored? Had more fun things to do? Where did you go<\/em>?<\/p>\n

With Claude, you can ask it to absorb a previous conversation, but Siri AI said, “Naw, no can do, man.” I may have said a non-Girlscout-safe word.<\/p>\n

I gave it some context in a new conversation, and it successfully helped me install Ubuntu. When I went to the URL of my Synology on my Tailscale with the correct port, I was greeted with a very pretty desktop and<\/em> an actual applications folder. I found what it called “Web browser” with no branding, but I saw it defaulted to DuckDuckGo for searching, so I knew I was in a happy place.<\/p>\n

\"Ubuntu
Ubuntu for the Win<\/figcaption><\/figure>\n

At this point, I sent a note to the Podfeet community in our Slack<\/a> saying, “I HAVE MADE FIRE!” Now all I had to do was install Blip by going to blip.net<\/a>. Easy peasy, right?<\/p>\n

Seventh Circle of Hell<\/h2>\n

At blip.net, if you select Linux as your operating system, you see two shiny buttons to run the installer from a GUI: “Get it on Flathub” and “Get it from the Snap Store”. Below that are three tabs: Arch, Nix, and Other. <\/p>\n

\"Install
Install Options for Blip on Linux<\/figcaption><\/figure>\n

I asked Siri AI to explain the options. I learned that Flathub is a community-driven store that is the preferred choice for non-Ubuntu distros. Snap Store is developed by Canonical (the company behind Ubuntu). That Snap Store option sounds dandy.<\/p>\n

But dandy it was not. When I tried to install Blip from the Snap Store, I was greeted by an alert that said, “The specified location is not supported. snap:\/\/blip” with no options but to close. How rude!<\/p>\n

\"Failed
Fail Store!<\/figcaption><\/figure>\n

Siri AI suggested I try installing Blip from the Snap Store, but this time from the command line. It gave me the very easy command: snap install blip<\/code>. But this threw an error: “snap: command not found”. Silly goose, everyone knows that you have to install snapd with apt install snapd<\/code> first. Now, can I install Blip with the snap command? Nope. Long, gloppy error telling me it can’t be done.<\/p>\n

\n error: cannot communicate with server: Post “http:\/\/localhost\/v2\/snaps\/blip”: dial unix \/run\/snapd.socket: connect: no such file or directory\n<\/p><\/blockquote>\n

At this point, Siri AI confessed that installing from the Snap Store will never succeed because I’m working in a containerized environment. As my friend Pat Dengler likes to say, “Le sigh.”<\/p>\n

But remember those three tabs I mentioned: Arch, Nix, and Other? Each of those has a command line method of installation for different Linux distros. Evidently, Ubuntu is considered “Other”. In that tab was a relatively familiar curl<\/code> command to fetch and run a shell script to install Blip.<\/p>\n

curl -fsSL https:\/\/static.blip.net\/linux\/install.sh | bash<\/code><\/p>\n

That threw an error, “Function not implemented”, which Siri AI told me was an error during the tar extraction (like opening a zip file). Guess what? It’s not supported by the underlying file system in my container. Cool cool.<\/p>\n

At this point, would you have stopped and given up? Absolutely, and I would have supported your decision. But I still had that Flathub button I could try for the installation, so I soldiered on.<\/p>\n

I was not to be rewarded for my tenacity. Clicking the Flathub button returned:<\/p>\n

flatpak remote-add command not found<\/code>.<\/p>\n

Eventually Claude explained that this is a “known issue when trying to run modern sandboxed applications (like Flatpaks) inside older or incompatible container environments.” Now where have I heard that before?<\/p>\n

Sidebar to talk about Selkies Clipboard Manager<\/h3>\n

I’m going to take an interlude from the main plot to explain something really interesting about this installation of Ubuntu. Remember that I’m working almost entirely on the advice of an AI, which means I need to copy and paste error messages and new commands back and forth between macOS and Ubuntu. Any hopes of doing \u2318C and \u2318V between them were quickly dashed.<\/p>\n

Siri AI told me to look for a short, vertical red line on the left edge of the screen. This opened a set of options in a vertical column with the name Selkies at the top. The helpful section was entitled Clipboard.<\/p>\n

This little window would accept a paste using the standard \u2318V from the Mac side. Once I pasted a command in there, I could use \u2303\u21e7V to paste into the Terminal in Ubuntu. To copy and paste in the other direction, I had to use \u2303\u21e7C in Ubuntu, \u2303\u21e7V to paste into the clipboard manager, and then \u2318V on the Mac.<\/p>\n

It was certainly clumsy and very easy to get your brain broken remembering which OS I was talking to, but it was easier and less error-prone than typing in arcane commands.<\/p>\n

\"Clipboard
Selkies Clipboard Manager<\/figcaption><\/figure>\n

I don’t actually know what Selkies is<\/em>, but I know it gives me a clipboard manager so that’s cool.<\/p>\n

Back on Topic<\/h2>\n

Ok, where were we? Snap Store didn’t work, Flatpak didn’t work, Curl didn’t work … and then Siri ended the conversation again<\/em>.<\/p>\n

\"screenshot
Siri Took Her Ball and Went Home<\/figcaption><\/figure>\n

Siri AI does a great job … until it doesn’t.<\/p>\n

I started this whole exercise at 1:45 PM. Other than taking a 15-minute break to watch my grandson practice hitting a baseball off of a T he got for his birthday, I’d been working on this pretty much non-stop.<\/p>\n

It was 4:04 PM when I switched to Claude. I gave it some context, and it wanted to try all of the same paths I’d tried before. But it did have one idea. It explained that the errors I was running into could be eliminated if I just flipped a little switch for the container: “Execute container using high privilege”.<\/p>\n

This is where I used my one superpower dealing with AI. When it tells you to do something you don’t understand, ask it what could go wrong, or if it’s dangerous.<\/p>\n

When it suggested I give the container high privilege, I said, “That sounds like I’d be circumventing a safety measure”. Claude answered:<\/p>\n

\n You\u2019re right. Privileged mode gives the container broad access to the NAS, so I wouldn\u2019t use it for this. Skip that.\n<\/p><\/blockquote>\n

Sheesh.<\/p>\n

But then it finally came up with an answer. Remember I had used the curl<\/code> command to download a tarball, but it wouldn’t unzip? Claude said,<\/p>\n

\n GNU tar is the likely culprit, since it uses newer syscalls your container blocks. Python\u2019s tarfile uses older, plainer calls.\n<\/p><\/blockquote>\n

And then gave me the command to open the tarball and extract all.<\/p>\n

mkdir -p \/config\/blip-py && python3 -c \"import tarfile; tarfile.open('\/config\/Desktop\/blip-1.2.6-linux-amd64.tar.gz').extractall('\/config\/blip-py')\" && ls \/config\/blip-py\/blip-1.2.6\/bin<\/code><\/p>\n

When that command did not<\/em> throw an error, it said to launch Blip with the command:<\/p>\n

\/config\/blip-py\/blip-1.2.6\/bin\/blip<\/code><\/p>\n

AND IT WORKED! I did a happy dance, for sure. I asked it to write me an alias so I could just use the command blip<\/code> instead of all that glop.<\/p>\n

Technically, my shiny new Blip works, but it’s not exactly elegant. First of all, I’m launching it from the command line, and it also glops incomprehensible text all over the terminal before launching. I did enjoy that it wrote BLIP in ASCII text for me in the middle of all that glop.<\/p>\n

\"Blip
Blip Launching in Ubuntu<\/figcaption><\/figure>\n

After that, I was rewarded with the Blip GUI, where I was able to send a file from Linux on the Synology over to my MacBook Air.<\/p>\n

\"Standard
Success!<\/figcaption><\/figure>\n

The time was 4:17 PM. Subtracting out the T-ball practice, that’s two hours and fifteen minutes from concept to success. For something entirely unnecessary. But boy, was I proud of myself.<\/p>\n

Epilogue<\/h2>\n

After we returned home, while drinking my morning coffee, I was noodling how nerdy this whole path was, and wondered if there wasn’t a container that was more like “real” Ubuntu, not this linuxserver\/webtop thingy. It’s really pretty janky with tiny icons and itty-bitty close buttons on the windows and all this command line glop. I asked Claude whether there was an easier way.<\/p>\n

It suggested I just use a Virtual Machine, not a Docker container! Synology has an app called Virtual Machine Manager, and in about 15 minutes I had a much cleaner, “real” version of Ubuntu running on my Synology. And most importantly, it had something called App Center, which accesses the Snap Store, and it had a one-click install of Blip!<\/p>\n

\"Ubuntu
Real Ubuntu<\/figcaption><\/figure>\n

I mentioned to Toma\u017e, the developer of Blip, what I had attempted to do and he told me they’re working on creating a pre-built container for Blip just for NAS devices. Isn’t that amazing?<\/p>\n

Bottom Line<\/h2>\n

I don’t regret the adventure at all, because I had a lot of fun. Did I need to do any of this? Nope. Would I do something like it again in the future? Absolutely, I would.<\/p>\n","protected":false},"excerpt":{"rendered":"

You know the phrase, “Just because you can do something, that doesn’t mean you should“? I think there needs to be another phrase, something like, “Just because you might be able to do something, you should try.” That’s the way I feel about the nearly two and a half hours I spent over the weekend […]<\/p>\n","protected":false},"author":1,"featured_media":36889,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_post_was_ever_published":false},"categories":[147],"tags":[8447,8445,2653,8446,2041,8448,2662],"class_list":["post-36881","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog-posts","tag-alpine-linux","tag-blip","tag-containers","tag-docker-container","tag-ubuntu","tag-ubuntu-linux","tag-virtual-machine"],"jetpack_sharing_enabled":true,"jetpack_featured_media_url":"https:\/\/www.podfeet.com\/blog\/wp-content\/uploads\/2026\/10\/BLIP-ASCII-1040x520-1.png","_links":{"self":[{"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/posts\/36881","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/comments?post=36881"}],"version-history":[{"count":2,"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/posts\/36881\/revisions"}],"predecessor-version":[{"id":36888,"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/posts\/36881\/revisions\/36888"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/media\/36889"}],"wp:attachment":[{"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/media?parent=36881"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/categories?post=36881"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/tags?post=36881"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}