github-starred/firejail

Fork 0

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

[GH-ISSUE #448] Building on ARM #323

New issue

Closed

opened 2026-05-05 05:36:01 -06:00 by gitea-mirror · 6 comments

gitea-mirror commented

2026-05-05 05:36:01 -06:00

Owner

Originally created by @lepasserby on GitHub (Apr 17, 2016).
Original GitHub issue: https://github.com/netblue30/firejail/issues/448

Hi!
I need to build firejail for Cubieboard 2 (CPU is A20, a dualcore Cortex A7) from source.
OS will likely be notoriously kvetchy Cubian (I could try Ubuntu but with GUI it's a mite too taxing the poor little ARM thing)

Is it possible? Should I look out for something in particular?

Originally created by @lepasserby on GitHub (Apr 17, 2016). Original GitHub issue: https://github.com/netblue30/firejail/issues/448 Hi! I need to build firejail for Cubieboard 2 (CPU is A20, a dualcore Cortex A7) from source. OS will likely be notoriously kvetchy Cubian (I could try Ubuntu but with GUI it's a mite too taxing the poor little ARM thing) Is it possible? Should I look out for something in particular?

gitea-mirror

2026-05-05 05:36:01 -06:00

closed this issue
added the
information_old
label

gitea-mirror commented

2026-05-05 05:36:05 -06:00

Author

Owner

@reinerh commented on GitHub (Apr 17, 2016):

Debian provides firejail also for armhf/armel/arm64 [1], so yes, it's possible.

1: https://packages.debian.org/unstable/firejail

@reinerh commented on GitHub (Apr 17, 2016): Debian provides firejail also for armhf/armel/arm64 [1], so yes, it's possible. 1: https://packages.debian.org/unstable/firejail

gitea-mirror commented

2026-05-05 05:36:09 -06:00

Author

Owner

@figue commented on GitHub (Apr 17, 2016):

I'm running firejail in a Cubietruck (A20) with a mainline kernel 4.4.7:

[root@suntk ~]# uname -a
Linux suntk 4.4.7 #2 SMP Sun Apr 17 19:43:47 CEST 2016 armv7l GNU/Linux

Firejail works, but it seems that seccomp is not detected or can't be enabled for a reason I don't know:

Warning: seccomp disabled, it requires a Linux kernel version 3.5 or newer.

@netblue30 can you confirm if seccomp should work in an arm system? I have enabled this option in kernel config:

[root@suntk ~]# zgrep SECCOMP /proc/config.gz 
CONFIG_SECCOMP=y

@figue commented on GitHub (Apr 17, 2016): I'm running firejail in a Cubietruck (A20) with a mainline kernel 4.4.7: ``` [root@suntk ~]# uname -a Linux suntk 4.4.7 #2 SMP Sun Apr 17 19:43:47 CEST 2016 armv7l GNU/Linux ``` Firejail works, but it seems that seccomp is not detected or can't be enabled for a reason I don't know: `Warning: seccomp disabled, it requires a Linux kernel version 3.5 or newer.` @netblue30 can you confirm if seccomp should work in an arm system? I have enabled this option in kernel config: ``` [root@suntk ~]# zgrep SECCOMP /proc/config.gz CONFIG_SECCOMP=y ```

gitea-mirror commented

2026-05-05 05:36:10 -06:00

Author

Owner

@reinerh commented on GitHub (Apr 17, 2016):

You are missing CONFIG_SECCOMP_FILTER.

@reinerh commented on GitHub (Apr 17, 2016): You are missing CONFIG_SECCOMP_FILTER.

gitea-mirror commented

2026-05-05 05:36:11 -06:00

Author

Owner

@netblue30 commented on GitHub (Apr 18, 2016):

Yes, seccomp works fine on ARM. There seem to be another kernel setting, CONFIG_HAVE_ARCH_SECCOMP_FILTER=y:

$ grep -i seccomp /boot/config-*
/boot/config-3.16.0-4-amd64:CONFIG_HAVE_ARCH_SECCOMP_FILTER=y
/boot/config-3.16.0-4-amd64:CONFIG_SECCOMP_FILTER=y
/boot/config-3.16.0-4-amd64:CONFIG_SECCOMP=y
/boot/config-4.3.0-0.bpo.1-amd64:CONFIG_HAVE_ARCH_SECCOMP_FILTER=y
/boot/config-4.3.0-0.bpo.1-amd64:CONFIG_SECCOMP_FILTER=y
/boot/config-4.3.0-0.bpo.1-amd64:CONFIG_SECCOMP=y

@netblue30 commented on GitHub (Apr 18, 2016): Yes, seccomp works fine on ARM. There seem to be another kernel setting, CONFIG_HAVE_ARCH_SECCOMP_FILTER=y: ``` $ grep -i seccomp /boot/config-* /boot/config-3.16.0-4-amd64:CONFIG_HAVE_ARCH_SECCOMP_FILTER=y /boot/config-3.16.0-4-amd64:CONFIG_SECCOMP_FILTER=y /boot/config-3.16.0-4-amd64:CONFIG_SECCOMP=y /boot/config-4.3.0-0.bpo.1-amd64:CONFIG_HAVE_ARCH_SECCOMP_FILTER=y /boot/config-4.3.0-0.bpo.1-amd64:CONFIG_SECCOMP_FILTER=y /boot/config-4.3.0-0.bpo.1-amd64:CONFIG_SECCOMP=y ```

gitea-mirror commented

2026-05-05 05:36:13 -06:00

Author

Owner

@figue commented on GitHub (Apr 18, 2016):

Thanks, I had to disable CONFIG_OABI_COMPAT to enable the other settings. It was a bit hard to figure it out. Now, warning message is gone and seccomp seems to work.

@figue commented on GitHub (Apr 18, 2016): Thanks, I had to disable CONFIG_OABI_COMPAT to enable the other settings. It was a bit hard to figure it out. Now, warning message is gone and seccomp seems to work.

gitea-mirror commented

2026-05-05 05:36:15 -06:00

Author

Owner

@netblue30 commented on GitHub (Apr 19, 2016):

CONFIG_OABI_COMPAT also seems to be disabled in Debian kernels.

@netblue30 commented on GitHub (Apr 19, 2016): CONFIG_OABI_COMPAT also seems to be disabled in Debian kernels.

gitea-mirror referenced this issue

2026-05-05 10:04:23 -06:00

[PR #323] [MERGED] Fix manual typo #3599

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#323

No description provided.

Rows
Columns