favicon here hometagsblogmicrobio cvtech cvgpg keys

Calling Executables Outside Distrobox That Are From Another Distrobox

#container #distrobox #podman

Soc Virnyl Estela | 2023-08-06 | updated: 2024-01-30 |reading time: ~3min

Update§

This old post is outdated and requires a small update. To run an executable from another container (here we use distrobox, a frontend for podman or docker), you just need to run this command inside the desired container where you want to run the executable.

sudo ln /usr/bin/distrobox-host-exec /usr/local/bin/my-executable

Make sure that the my-executable was already distrobox-exported to the host.

Old post§

To anyone that might have asked themselves

How do I call an executable from Y distro to the current X distro I am using in distrobox?

The answer is to create a script. But first you will have to use distrobox-host-exec. Create a symlink inside your distrobox. You can either declare an init-hook or do it manually. The command is

ln -sf distrobox-host-exec /usr/local/bin/podman

This will create a pseudo podman executable that will run the host system's podman, assuming you have that installed in your host system.

To check if it works, run

podman ps

This will give you a list of available containers that are active.

Example situation§

So let's assume you are in a weird situation. You want to use zig but the one on openSUSE Tumbleweed distrobox is 0.10.0 because it has an issue with glibc versions. But it builds correctly on openSUSE Leap 15.5! The next thing you did was to create your leap distrobox

distrobox-create -i leap:latest -n leap

And then you ran the following command inside your leap distrobox

sudo zypper addrepo https://download.opensuse.org/repositories/devel:tools:compiler/15.5/devel:tools:compiler.repo
sudo zypper refresh
sudo zypper install zig

So uh... how do I use zig from leap when I am in a tumbleweed distrobox?

By using distrobox-host-exec which calls your podman executable! Remember the symlink? Here is the idea

podman has an exec command. Running podman exec --help gives you the following output:

Run a process in a running container

Description:
  Execute the specified command inside a running container.


Usage:
  podman exec [options] CONTAINER [COMMAND [ARG...]]

Examples:
  podman exec -it ctrID ls
  podman exec -it -w /tmp myCtr pwd
  podman exec --user root ctrID ls

Options:
  -d, --detach               Run the exec session in detached mode (backgrounded)
      --detach-keys string   Select the key sequence for detaching a container. Format is a single character [a-Z] or ctrl-<value> where <value> is one of: a-z, @, ^, [, , or _ (default "ctrl-p,ctrl-q")
  -e, --env stringArray      Set environment variables
      --env-file strings     Read in a file of environment variables
  -i, --interactive          Keep STDIN open even if not attached
  -l, --latest               Act on the latest container podman is aware of
                             Not supported with the "--remote" flag
      --preserve-fds uint    Pass N additional file descriptors to the container
      --privileged           Give the process extended Linux capabilities inside the container.  The default is false
  -t, --tty                  Allocate a pseudo-TTY. The default is false
  -u, --user string          Sets the username or UID used and optionally the groupname or GID for the specified command
  -w, --workdir string       Working directory inside the container

Since it says here that we can run a process from a running container, we can create a script to run zig in your tumbleweed distrobox!

#!/bin/bash
/usr/local/bin/podman exec --user $USER -it -w $PWD leap zig $@

And save it to /usr/local/bin/zig and run sudo chmod +x /usr/local/bin/zig.

Testing your zig executable§

Inside your tumbleweed distrobox which now contains your pseudo zig executable, you can test if it works by doing the commands

md hello-zig/
cd $_
zig init-exe
zig build
./zig-out/hello-zig

The last command should output

All your codebase are belong to us.
Run `zig build test` to run the tests.

How it works§

We have distrobox-host-exec (which calls host-spawn in the background), and podman. By using distrobox-host-exec to run the host system podman, we can also check other running containers, not just from leap distrobox in the previous examples.

With podman, we can use its exec command to run executables from other containers. The important flags are

  • -w or --workdir. This is where you set $PWD
  • -i or --interactive. This allows interactivity
  • -t or --tty. This will allow it to work somewhat okay-ish in a terminal.

Plus $@ to add possible other subcommands of an executable e.g. build, test, --help.

The --user is set to $USER so it respects your user inside the container. Otherwise, it will become root which maybe is not what you want.

So the final and cool command for the pseudo zig executable is:

#!/bin/bash

# leap can be anything: container ID or container NAME
/usr/local/bin/podman exec --user $USER -it -w $PWD leap zig $@

More information§

You can find more information from the following links:

Articles from blogs I follow around the net

GreyNoise Labs Weekly OAST (Well-known Out-of-band Interaction Domains) Report • Week Ending 2026-01-13

Overview GreyNoise sensors captured extensive scanning activity targeting web application vulnerabilities with Out-of-band Application Security Testing (OAST) callback domains embedded in exploit payloads. The activity spanned seven days with peak concent…

via GreyNoise LabsJanuary 24, 2026

The Birthday Paradox, simulated

I'm a fan of simulating counterintuitive statistics. I recently did this with the Monty Hall problem and I really enjoyed how it turned out. A similarly interesting statistical puzzle is the birthday paradox: you only need to get 23 people in a room a room…

via pcloadletterJanuary 23, 2026

Status update, January 2026

Hi! Last week I’ve released Goguma v0.9! This new version brings a lot of niceties, see the release notes for more details. New since last month are audio previews implemented by delthas, images for users, channels & networks, and usage hints when typing a…

via emersionJanuary 21, 2026

The Only Two Markup Languages

There are only two families of proper arbitrary markup languages: TeX and SGML I would normally link to official thing as reference but it's behind the "wonderful" ISO paywall: ISO 8879:1986.. By arbitrary, I mean the grammar specifically, and how it can …

via gingerBill - ArticlesJanuary 19, 2026

Software Assurance & That Warm and Fuzzy Feeling

If I were to recommend you use a piece of cryptography-relevant software that I created, how would you actually know if it was any good? Trust is, first and foremost, a social problem. If I told you a furry designed a core piece of Internet infrastructure,…

via Dhole MomentsJanuary 15, 2026

Redesigning my microkernel from the ground up

As you may recall, circa 2022-2023 I was working on a microkernel written in Hare named Helios. Helios was largely inspired by and modelled after the design of seL4 and was my first major foray into modern OS development that was serious enough to get to a…

via Drew DeVault's blogJanuary 12, 2026

I transformed my LEGO Gameboy into a working Gameboy!

Since I saw the Lego Gameboy set, I wanted to make it functional since I have good knowledge of programming and little knowledge of electronics. Also I've been a big fan of Gameboys since I was a kid, so I thought it would be a fun project to combine my…

via Christian Visintin BlogJanuary 06, 2026

Gbyte leaks gigabytes of data - #FuckStalkerware pt. 8

plus an MMO boosting service, fully remote Android spying and patented ToS violations

via maia blogJanuary 06, 2026

Whiplash and the ideas of success

Some ideas about success and analysis of some of the concepts of the film Whiplash

via Ishan WritesJanuary 04, 2026

reqwest v0.13 - rustls by default

To end out the year, here comes a new major release of reqwest, the opinionated higher-level HTTP client for Rust. We don’t really need major breaking versions to keep providing value. Improvements keep coming all the time. But we did need one to make one…

via seanmonstarDecember 30, 2025

Merry Christmas, Ya Filthy Animals (2025)

It’s my last day of writing for the year, so I’m going to try keep this one quick – it was knocked out over three hours, so I hope you can forgive me if it’s a bit clumsier than my usual writing. For some strange reason, one of the few clear memories I hav…

via LudicityDecember 27, 2025

Are people migrating away from GitHub?

I noticed some people migrating away from GitHub recently. I was curious to understand the rationale. Is it a blip or is it a sign of prolonged exodus?

via Rob O'Leary | BlogDecember 22, 2025

Yep, Passkeys Still Have Problems

It's now late into 2025, and just over a year since I wrote my last post on Passkeys. The prevailing dialogue that I see from thought leaders is "addressing common misconceptions" around Passkeys, the implication being that "you just don't understand it co…

via Firstyear's blog-a-logDecember 17, 2025

Theme selector

Two weeks ago I added dark mode to this website. It was late one night and I was revisiting an article and my eyes were tired, so that was that. It was based solely on system dark mode settings, and I started using some more nice, modern CSS features like …

via macwright.comDecember 09, 2025

Testing multiple versions of Python in parallel

Daniel Roy Greenfeld wrote about how to test your code for multiple versions of Python using `uv`. I follow up with a small improvement to the Makefile.

via Technically PersonalJuly 21, 2025

LLDB's TypeSystems Part 2: PDB

In my previous post, I described implementing PDB parsing as a can of worms. That might have been a bit of an understatement. PDB has been one "oh, it's gonna be twice as much work as I thought" after another. Implementing it has revealed many of the same …

via Cracking the ShellJuly 07, 2025

#Rx Writing Challenge 2025

This is a short reflection on my experience of the recent writing challenge I took part in. Over the past two weeks, I have participated in the #RxWritingChallenge 1—a daily, 30-minute writing group starting at 9 AM every morning. Surrounded by fellow doct…

via Ul-lingaApril 05, 2025

My coffee workflow

My coffee workflow by Clement Delafargue on April 1, 2025 Tagged as: coffee, espresso, flair58, v60. It is my first April cools’ and I guess I could start by talking about coffee. If you’ve seen me in person, it won’t be a surprise, I guess. This po…

via Clément Delafargue - RSS feedApril 01, 2025

Generated by openring-rs

favicon here hometagsblogmicrobio cvtech cvgpg keys