Belajar Agar Berkembang

Rabu, 02 April 2025

5 Tools to Enhance Your AppImage Experience on Linux

The portable AppImage format is quite popular among developers and users alike. It allows you to run applications without installation or dependency issues, on virtually any Linux distribution.

However, managing multiple AppImages or keeping them updated can sometimes be a bit cumbersome. Fortunately, there are third-party tools that simplify the process, making it easier to organize, update, and integrate AppImages into your Linux system.

In this article, I’ll share some useful tools that can help you manage AppImages more effectively and enhance your overall experience.

Gear Lever

Gear Lever is a modern GTK-based application that lets you manage your local AppImage files. It primarily helps you organize AppImages by adding desktop entries, updating applications, and more.

Features of Gear Lever

Drag and drop files directly from your file manager
Update apps in place
Keep multiple versions installed

Install Gear Lever

Gear Lever is available as a Flatpak package. You can install it with the following command:

flatpak install flathub it.mijorus.gearlever

Gear Lever

AppImage Launcher

📋

While the last release of AppImage Launcher was a few years ago, it works pretty fine.

If you're a frequent user of AppImage packages, you should definitely check out AppImage Launcher. This open-source tool helps integrate AppImages into your system.

It allows users to quickly add AppImages to the application menu, manage updates, and remove them with just a few clicks.

Features of AppImage Launcher

Adds desktop integration to AppImage files
Includes a helper tool to manage AppImage updates
Allows easy removal of AppImages
Provides CLI tools for terminal-based operations and automation

Install AppImage Launcher

For Ubuntu users, the .deb file is available under the Continuous build section on the releases page.

AppImage Launcher

AppImage Package Manager and AppMan

AppImage Package Manager (AM) is designed to simplify AppImage management, functioning similarly to how APT or DNF handle native packages. It supports not just AppImages, but other portable formats as well.

AM relies on a large database of shell scripts, inspired by the Arch User Repository (AUR), to manage AppImages from various sources.

A similar tool is AppMan. It is basically AM but manages all your apps locally without needing root access.

If you are a casual user, you can use AppMan instead of AM so that everything will be local and no need for any sudo privileges.

AppImage Package Manager (AppMan Version)

Features of AppImage Package Manager

Supports AppImages and standalone archives (e.g., Firefox, Blender)
Includes a comprehensive shell script database for official and community-sourced AppImages
Create and restore snapshots
Drag-and-drop AppImage integration
Convert legacy AppImage formats

Install AppImage Package Manager

To install, run the following commands:

wget -q https://raw.githubusercontent.com/ivan-hc/AM/main/AM-INSTALLER && chmod a+x ./AM-INSTALLER && ./AM-INSTALLER

The installer will prompt you to choose between AM and AppMan. Choose AppMan if you prefer local, privilege-free management.

AppImage Package Manager

AppImagePool

AppImagePool is a Flutter-based client for AppImage Hub. It offers a clean interface to browse and download AppImages listed on AppImage Hub.

Features of AppImagePool

Categorized list of AppImages
Download from GitHub directly, no extra-server involved
Integrate and Disintegrate AppImages easily from your system
Version History and multi download support

Installing AppImage Pool

Download the AppImage file from the official GitHub releases page.

Download AppImage Pool

There is a Flatpak package is available to install from Flathub. If your system has Flatpak support, use the command:

flatpak install flathub io.github.prateekmedia.appimagepool

Zap

📋

The last release of Zap was a few years ago but it worked fine in my testing.

Zap is an AppImage package manager written in Go. It allows you to install, update, and integrate AppImage packages efficiently.

0:00

/0:37

Zap AppImage package Manager

Features of Zap

Install packages from the AppImage catalog using registered names
Select and install specific versions
Use the Zap daemon for automatic update checks
Install AppImages from GitHub releases

Install Zap

To install Zap locally, run:

curl https://raw.githubusercontent.com/srevinsaju/zap/main/install.sh | bash -s

For a system-wide installation, run:

curl https://raw.githubusercontent.com/srevinsaju/zap/main/install.sh | sudo bash -s

Zap

In the end...

Here are a few more resources that an AppImage lover might like:

Bauh package manager: bauh is a graphical interface for managing various Linux package formats like AppImage, Deb, Flatpak, etc.
XApp-Thumbnailers: This is a thumbnail generation tool for popular file managers.
Awesome AppImage: Lists several AppImage tools and resources.

AppImage is a fantastic way to use portable applications on Linux, but managing them manually can be tedious over time. Thankfully, the tools mentioned above make it easier to organize, update, and integrate AppImages into your workflow.

From a feature-rich GUI tool like Gear Lever to CLI tools like AppImagePool and AppMan, there’s something here for every kind of user. Try out a few and see which one fits your style best.

from It's FOSS https://ift.tt/V9azPMk
via IFTTT

Rabu, 26 Maret 2025

FOSS Weekly #25.13: Kernel 6.14, Zorin 17.3, EU OS, apt Guide and More Linux Stuff

Rust in Linux kernel is not news. You already know about that. But Rust in GNU is a big move.

It seems that a Rust rewrite of GNU's coreutils (meta package that gives us commands like cp, ls, dd, mv etc) will be included in Ubuntu's upcoming release.

This concerns many hardcore Free Software supporters, as they see it a move to take GNU out of GNU Linux.

What are your thoughts on it?

💬 Let's see what else you get in this edition

Chimera Linux moving away from RISC-V.
Beginner's guide to apt command.
A new community Linux distro being proposed for the EU.
Linux kernel 6.14 releasing with many refinements.
And other Linux news, tips, and, of course, memes!
This edition of FOSS Weekly is supported by PikaPods.

❇️ PikaPods: Enjoy Self-hosting Hassle-free

PikaPods allows you to quickly deploy your favorite open source software. All future updates are handled automatically by PikaPods while you enjoy using the software. PikaPods also share revenue with the original developers of the software.

You get a $5 free credit to try it out and see if you can rely on PikaPods. I know, you can 😄

📰 Linux and Open Source News

Flowblade 2.20 has been released with many changes.
Forge1 is ArmSoM's latest offering for embedded use.
Chimera Linux no longer supports the RISC-V CPU architecture.
Ubuntu has added official support for NVIDIA Jetson AI modules.
Fauna database has shut down, but there are talks of open sourcing it.
Zorin OS 17.3 release replaces Firefox with Brave.
Freedesktop SDK removes OpenH264 due to maintenance issues.

Linux kernel 6.14 has arrived with performance gains and new support:

🧠 What We’re Thinking About

A new community-led initiative called “EU OS” to develop a Linux distribution initiative looks like a positive development.

🧮 Linux Tips, Tutorials and More

LibreOffice users should know these tips to get more out of it.
pacman -Syu is an important command to know on Arch Linux.
Learn how to check free disk space on Linux via the terminal or GUI.

👷 Homelab and Maker's Corner

Run Ollama on Docker and take your AI workflow anywhere.

✨ Apps Highlight

Do you want a tool that helps with the management of your Linux system?

📽️ Videos I am Creating for You

Learn about modern alternatives to the classic Linux commands in the latest video.

Subscribe to It's FOSS YouTube Channel

🧩 Quiz Time

Do you know all of these legendary coders?

Also, a new crossword on discontinued Linux distros.

💡 Quick Handy Tip

In GNOME, you can use the Auto Move Windows extension to automatically open new app windows in specific workspaces. First, install it either from the webpage, or via Extension Manager.

In the extension settings page, select the windows and the corresponding workspace to automatically move new windows into workspaces. Now, new windows should appear in their designated workspaces.

🤣 Meme of the Week

This is heartbreaking 💔

🗓️ Tech Trivia

On March 24, 1896, Russian physicist Aleksandr Popov successfully transmitted radio signals over 250 meters between buildings at St. Petersburg University. This achievement followed his 1895 presentation of a wireless lightning detector.

🧑‍🤝‍🧑 FOSSverse Corner

Regular FOSSer Paul is pondering a switch to a 64-bit system on a local priest's computer. Can you help?

❤️ With love

Share it with your Linux-using friends and encourage them to subscribe (hint: it's here).

Share the articles in Linux Subreddits and community forums.

Opt for It's FOSS Plus membership and support us 🙏

Enjoy FOSS 😄

from It's FOSS https://ift.tt/RkioWmZ
via IFTTT

Selasa, 25 Maret 2025

Setting Up Ollama With Docker

Ollama has been a game-changer for running large language models (LLMs) locally, and I've covered quite a few tutorials on setting it up on different devices, including my Raspberry Pi.

But as I kept experimenting, I realized there was still another fantastic way to run Ollama: inside a Docker container.

Now, this isn’t exactly breaking news. The first Ollama Docker image was released back in 2023. But until recently, I always used it with a native install.

It wasn’t until I was working on an Immich tutorial that I stumbled upon NVIDIA Container Toolkit, which allows you to add GPU support to Docker containers.

That was when I got hooked on the idea of setting up Ollama inside Docker and leveraging GPU acceleration.

In this guide, I’ll walk you through two ways to run Ollama in Docker with GPU support:

Using a one liner docker run command.
With Docker compose

Now, let’s dive in.

📋

Before we get started, if you haven’t installed Docker yet, check out our previous tutorials on setting up Docker on Linux.

Prerequisite: Installing Nvidia Container toolkit

The NVIDIA Container Toolkit includes the NVIDIA Container Runtime and the NVIDIA Container Toolkit plugin for Docker, which enable GPU support inside Docker containers.

Before installation, make sure that you have already installed the GPU drivers on your specific distro.

Now, to install the NVIDIA Container Toolkit, follow these steps:

Enable the NVIDIA CUDA repository on your system by running the following commands in a terminal window:

distribution=$(. /etc/os-release;echo $ID$VERSION_ID)
curl -s -L https://nvidia.github.io/nvidia-docker/gpgkey | sudo apt-key add -
curl -s -L https://nvidia.github.io/nvidia-docker/$distribution/nvidia-docker.list | sudo tee /etc/apt/sources.list.d/nvidia-docker.list
sudo apt update

Install the NVIDIA Container Toolkit by running the following command in a terminal window:

sudo apt install -y nvidia-container-toolkit

Restart the Docker service to apply the changes:

sudo systemctl restart docker

Method 1: Running Ollama with Docker run (Quick Method)

If you just want to spin up Ollama in a container without much hassle, this one-liner will do the trick:

docker run -d --name ollama -p 11434:11434 -v ollama:/root/.ollama ollama/ollama

Or, if you want the GPU support:

docker run -d --gpus=all -v ollama:/root/.ollama -p 11434:11434 --name ollama ollama/ollama

Here's a breakdown of what's going on with this command:

docker run -d: Runs the container in detached mode.
--name ollama: Names the container "ollama."
-p 11434:11434: Maps port 11434 from the container to the host.
-v ollama:/root/.ollama: Creates a persistent volume for storing models.
ollama/ollama: Uses the official Ollama Docker image.

Once the container is running, you can check its status with:

docker ps

Method 2: Running Ollama with Docker compose

I personally find that docker compose is a more structured approach when setting up a service inside a container, as it's much easier to manage.

💡

If you're setting up Ollama with Open WebUI, I would suggest to use docker volumes instead of bind mounts for a less frustrating experience.

We'll start with creating a docker-compose.yml file, to manage the Ollama container:

version: '3.8'

services:
  ollama:
    image: ollama/ollama
    container_name: ollama
    ports:
      - "11434:11434"
    volumes:
      - ollama:/root/.ollama
    deploy:
      resources:
        reservations:
          devices:
            - driver: nvidia
              count: all
              capabilities: [gpu]
    restart: unless-stopped

volumes:
  ollama:

With the docker-compose.yml file in place, start the container using:

docker-compose up -d

This will spin up Ollama with GPU acceleration enabled.

Accessing Ollama in Docker

Now that we have Ollama running inside a Docker container, how do we interact with it efficiently?

There are two main ways:

1. Using the Docker shell

This is really easy, you can access Ollama container shell by typing:

docker exec -it ollama <commands>

but typing this same command overtime can be tiring. We can create an alias to make it shorter.

Add this to your .bashrc file:

echo 'alias ollama="docker exec -it ollama ollama"' >> $HOME/.bashrc
source $HOME/.bashrc

and since I'm using zsh shell, I'll be using this command:

echo 'alias ollama="docker exec -it ollama ollama"' >> $HOME/.zshrc

Now, instead of typing the full docker exec command, you can just run:

ollama ps
ollama pull llama3
ollama run llama3

This makes interacting with Ollama inside Docker feel just like using a native install.

2. Using Ollama’s API with Web UI Clients

Ollama exposes an API on http://localhost:11434, allowing other tools to connect and interact with it.

If you prefer a graphical user interface (GUI) instead of the command line, you can use several Web UI clients.

Some popular tools that work with Ollama include:

Open WebUI – A simple and beautiful frontend for local LLMs.
LibreChat – A powerful ChatGPT-like interface supporting multiple backends.

We’ve actually covered 12 different tools that provide a Web UI for Ollama.

Whether you want something lightweight or a full-featured alternative to ChatGPT, there’s a UI that fits your needs.

Conclusion

Running Ollama in Docker provides a flexible and efficient way to interact with local AI models, especially when combined with a UI for easy access over a network.

I’m still tweaking my setup to ensure smooth performance across multiple devices, but so far, it’s working well.

On another note, diving deeper into NVIDIA Container Toolkit has sparked some interesting ideas. The ability to pass GPU acceleration to Docker containers opens up possibilities beyond just Ollama.

I’m considering testing it with Jellyfin for hardware-accelerated transcoding, which would be a huge boost for my media server setup.

Other projects, like Stable Diffusion or AI-powered upscaling, could also benefit from proper GPU passthrough.

That said, I’d love to hear about your setup! Are you running Ollama in Docker, or do you prefer a native install? Have you tried any Web UI clients, or are you sticking with the command line?

Drop your thoughts in the comments below.

from It's FOSS https://ift.tt/0UqnTkK
via IFTTT

Senin, 24 Maret 2025

Why do We Use pacman -Syu to System Update as Well as Package Installation in Arch Linux?

How do you update Arch Linux? You run sudo pacman -Syu command.

How do you install a package on Arch Linux? You run sudo pacman -Syu package_name.

Which might make you wonder why do you need a system update while installing a new package? What does those S, y and u do? Let me explain these things to you.

What does pacman -Syu does?

In simpler words, pacman -Syu updates all the installed packages on your Arch-based Linux distribution if they have a newer version available. Here, -S stands for sync or install, y refreshes the local package database cache with the remote repository and u will make a list of all the install packages that can be updated by referring to the local package database cache and getting actual packages from the remote repository.

Understanding pacman -Syu command

I hope you are familiar with the concept of package manager. If not, please refer to this explainer article:

Pacman package manager works pretty much the same. There is a remote repository that has the actual packages, a local package database that usually keeps the information about the packages by interacting with the remote repository. pacman is the command line interface that utilizes this structure to manage packages on your Arch Linux.

-S (capital letter S) is the main option and y and u are 'sub-options' supporting it.

S stands for sync but you can think of it as 'install'. It syncs your Arch Linux system with the remote repository for the given package. Meaning, both repository and local Arch system will be synced (at that time) for the given package. Which is another way of saying that the package is installed on the system.

You cannot just run pacman -S and expect it to sync (install) all the packages from the repositories on the local system. That would be disastrous if your system installs all 40,000+ packages of the remote repositories.

This is why you need to provide a target (package names) with only -S option. Otherwise, you'll see this error.

sudo pacman -S
error: no targets specified (use -h for help)

If you specify a package or group name, it will 'install' the package on your system.

There are additional options with Sync. You'll probably be using a lot of sudo pacman -Syu.

Those y and u are 'sub options' of -S. You cannot use them on their own like pacman -yu:

sudo pacman -yu
error: invalid option '-y'

While the order of S, y and u doesn't matter, there has to be an S with y and u.

The y sub-option of S refreshes the local package cache DB with remote repository. Then u sub-option is for sysupgrade which refers to the local package cache to make a list of all the installed packages that can be upgraded to a newer version.

With the work of these two sub options done, S (sync) will fetch the packages (newer versions) from the remote repository and install (update existing) them.

📋

Sometimes, I feel like it would have been better to use terms like install instead of sync and r for refresh instead of y. Easier to understand.

Why always run "pacman -Syu" even while installing a single package?

You'll notice that Arch package installation often mentions the pacman command in the following format:

sudo pacman -Syu package_name

And you may wonder what's the point of updating all the installed packages. Why not just do sudo pacman -Sy package_name which would be quicker as it will only install the package you want, not upgrade other packages that have newer versions available?

There is a pretty good reason for that. It helps avoid the dependency issues that could occur otherwise.

I liked the analogy in this Reddit discussion and I am going to use the same here as well.

Imagine an old-fashioned paper catalog folks used to get in the mail a few decades back. If you get a catalog in the mail from a store, it had a listing of everything the store had for sale and the current prices. The Arch package database is like this catalog. The catalog you have with you is the package database cache on your system.

The packages are like the actual goods you buy through the catalog. You find the item number that you want in the catalog, place the order, and the correct item is delivered.

Imagine you just run pacman -Sy. This is equivalent to getting the latest catalog.

Now, let's say you have an iPhone 14 (an outdated package) and you order an iPhone charger from the new catalog. You'll have a problem when the new charger arrives because the iPhone now uses the type C port instead of the old lightning port. A conflict arises.

If you had run pacman -Syu, you would have ordered both the newer iPhone and the correct charger with it.

(Don't take it literally and start commenting that it will be a financially stupid decision to order a new phone instead of the older charger. This is just for example 😜)

Conclusion

I don't know whether you were ever curious about it or not, but I do hope you have a slightly better understanding of the logic behind the famous -Syu option of pacman command. The man page is always there to read the official explanation of each option and its usage.

You can always explore more options of the pacman command to see what it can do for regular package management on Arch Linux.

🗨️ Did this article help you understand the 'sync' concept in Arch Linux, or are you more confused than before? Do let me know in the comment section.

from It's FOSS https://ift.tt/uay18oA
via IFTTT

Rabu, 19 Maret 2025

FOSS Weekly #25.12: GNOME 48 and GIMP 3.0 Released, Switching to IceWM, Ollama Commands and More Linux Stuff

We reached the 30,000 followers mark on Mastodon. This is an unexpected feat.

We have 140,000 people on our Twitter profile but that's because Twitter/X is a bigger platform. I am pleasantly surprised to see so many people on an alternative, decentralized platform like Mastodon.

If you use Mastodon, do join us there.

💬 Let's see what else you get in this edition

AntiX and IceWM reviving an old computer.
Roblox introducing a new open source AI model.
A new GIMP release arriving after a decade of development.
And other Linux news, tips, and, of course, memes!
This edition of FOSS Weekly is supported by ANY.RUN.

🤖 ANY.RUN’s Instant Android Threat Analysis Is Live – Now Available to Everyone

ANY.RUN’s Interactive Sandbox now supports Android OS, making mobile malware detection faster, smarter, and more effective in a secure, real-time environment.

Now your team can analyze Android malware behavior just like on a real device: interact with possible threats and speed up response times.

Be among the first to try this game-changing upgrade and help your team:

Expand threat visibility with real-time APK analysis
Reduce incident response times
Simplify threat hunting
Lower cybersecurity costs

…all from one convenient, cloud-based environment ☁️

Available for ALL plans, including Free. Start your first analysis now!

Interactive Online Malware Analysis Sandbox - ANY.RUN

Cloud-based malware analysis service. Take your information security to the next level. Analyze suspicious and malicious activities using our innovative tools.

ANY.RUN

📰 Linux and Open Source News

Zed editor now has native Git support.
cuOpt is NVIDIA's latest open source offering.
SystemRescue 12.00 has launched with the latest LTS kernel.
PINE64's updated PineTab-V now features a Debian-based distro.
Dash to Panel GNOME extension is looking for a new maintainer.
Roblox has unveiled Cube 3D, their open source AI model for 3D creation.
Steam's ongoing Spring Sale has some nice discounts on games that run on Linux.

GNOME 48 is here to bring a modern desktop experience to Linux.

After making us wait for 10 years, the GIMP 3.0 release has finally shown up with loads of improvements:

🧠 What We’re Thinking About

One of our community contributors switched from Xfce on EndeavourOS to IceWM on AntiX. They shared how it went.

🧮 Linux Tips, Tutorials and More

Quick tip on using AppImage applications as default.
You know you can watch Star Wars in the Linux terminal?
GNOME's Activity Search is more powerful than you think.
We now have IPv4 and IPv6, ever wondered what happened to IPv5?

👷 Homelab and Maker's Corner

Manage LLMs locally and easily by using Ollama commands.

✨ Apps Highlight

Keep track of the data usage on your Android smartphone with Data Monitor.

📽️ Videos I am Creating for You

I share how I dual booted CachyOS with Windows in this video.

Subscribe to It's FOSS YouTube Channel

🧩 Quiz Time

This fun crossword is for the fans of Debian... and/or Toy Story. And another one on open source licenses.

💡 Quick Handy Tip

In GNOME, you can add custom directories to GNOME Search. First open Settings and go to Search → Search Locations. Here, click on Add Locations and choose a location.

Now, add the locations you want to see as results in the overview. After that, whenever you search, these locations will appear in the results page if there's a match. In this quick demo, I just showed you how to do it, on your computer, avoid adding locations like /etc, /usr, etc.

🤣 Meme of the Week

The list is virtually non-existent at this point. 🙂

🗓️ Tech Trivia

On March 17, 1988, Apple sued Microsoft, claiming that Windows 2.0 copied the Macintosh GUI. Initially, a judge ruled that Microsoft had limited rights based on an earlier licensing agreement. The case went through appeals and eventually reached the U.S. Supreme Court, which declined to review it in 1995.

This decision effectively ended the legal battle, allowing Microsoft to continue using the Windows GUI.

🧑‍🤝‍🧑 FOSSverse Corner

An interesting read on the move by Ubuntu towards Rust.

❤️ With love

Share it with your Linux-using friends and encourage them to subscribe (hint: it's here).

Share the articles in Linux Subreddits and community forums.

Opt for It's FOSS Plus membership and support us 🙏

Enjoy FOSS 😄

from It's FOSS https://ift.tt/Gny5bXe
via IFTTT