github-starred/firejail

Fork 0

mirror of https://github.com/netblue30/firejail.git synced 2026-05-15 14:16:14 -06:00

[GH-ISSUE #5411] Firejail AppImage or Portable version of Firejail? #2988

New issue

Closed

opened 2026-05-05 09:38:40 -06:00 by gitea-mirror · 2 comments

gitea-mirror commented

2026-05-05 09:38:40 -06:00

Owner

Originally created by @AmyMoriyama on GitHub (Oct 11, 2022).
Original GitHub issue: https://github.com/netblue30/firejail/issues/5411

The request:
To be able to run firejail from any folder/directory (portable).

Suggested method:
Either an AppImage of firejail or a static binary.

Why?
It would be greatly useful in situations relating to portable applications. One example, let's say you have a USB stick with some AppImage apps on it, but you want to maintain control over those apps when ran. Having a copy of firejail on the USB stick along with the other portable apps could do this.

Originally created by @AmyMoriyama on GitHub (Oct 11, 2022). Original GitHub issue: https://github.com/netblue30/firejail/issues/5411 The request: To be able to run firejail from any folder/directory (portable). Suggested method: Either an AppImage of firejail or a static binary. Why? It would be greatly useful in situations relating to portable applications. One example, let's say you have a USB stick with some AppImage apps on it, but you want to maintain control over those apps when ran. Having a copy of firejail on the USB stick along with the other portable apps could do this.

gitea-mirror

2026-05-05 09:38:40 -06:00

closed this issue
added the
enhancement

duplicate
labels

gitea-mirror commented

2026-05-05 09:38:43 -06:00

Author

Owner

@rusty-snake commented on GitHub (Oct 11, 2022):

Having a copy of firejail on the USB stick along with the other portable apps could do this.

The stick needs an Linux filesystem like ext4, xfs, btrfs, … that support UNIX file permissions. NTFS, vFAT, FAT32, exFAT, ... do not work. And you need to mount this stick as root which usually mean you can not use a graphical filemanager. This is because firejail needs to be SUID. Therefore it may be less useless than you think.

Firejail AppImage

#2849

static binary

An firejail build w/o AppArmor/SELinux support only requires glibc and linker. So as long as the system you want to run firejail has a newer/the same glibc as the system you build firejail it should be able to run (!= work).

So the only problem that can be solved at build-time are the paths (profiles, plugins, config files).

@rusty-snake commented on GitHub (Oct 11, 2022): > Having a copy of firejail on the USB stick along with the other portable apps could do this. The stick needs an Linux filesystem like ext4, xfs, btrfs, … that support UNIX file permissions. NTFS, vFAT, FAT32, exFAT, ... do not work. And you need to mount this stick as root which usually mean you can not use a graphical filemanager. This is because firejail needs to be SUID. Therefore it may be less useless than you think. > Firejail AppImage #2849 > static binary An firejail build w/o AppArmor/SELinux support only requires glibc and linker. So as long as the system you want to run firejail has a newer/the same glibc as the system you build firejail it should be able to run (!= work). So the only problem that can be solved at build-time are the paths (profiles, plugins, config files).

gitea-mirror commented

2026-05-05 09:38:43 -06:00

Author

Owner

@kmk3 commented on GitHub (Sep 21, 2024):

Duplicate of #2849

@kmk3 commented on GitHub (Sep 21, 2024): Duplicate of #2849

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/firejail#2988

No description provided.

Rows
Columns