Requesting new packages / new versions

Hi @Comodore125,

Yes, running the latest version of docker from the alpine linux sources. It’s a bit of a pain, but working well so far apart from the missing kernel modules mentioned in another thread.

Search the forum for this post or just docker, and install the package that huibuhDec pulled together - then once installed, find the alpine docker APK, untar and copy the new bins / libs in place.


huibuhDec '17
Hey guys,

I manged to get docker running (more or less) on the Turris Omnia.

I used precompiled armhf binaries from the alpine linux distribution. To circumvent the networking problems described above (and a few more) you need to install following dependencies:

Here you can find a package compiled for the current released kernel version (4.4.91-e8cacce0ae0bf48eea19d58c2e860359-1):!tOJgGTTB!kUsQX7oC3DKDB6FWYd1nTts4ih-nEt8grv7XSzaonuw8


Ressource sharing: Since the required cgroups are not enabled in the stock kernel, the docker daemon has no way of limiting the consumption of certain resources for containers. So if you’re running resource hungry containers, they might starve others.
Swarm: There is (as far as I could find) no available IP_VS module and the kernel is compiled without support for it. If I remember correctly, this is required to set up the ingress network used by docker in swarm mode to route incoming packets. If you want your router to join a swarm, you will most probably need to compile it yourself (or ask me, I’ve got a working version for the current kernel but I am too lazy to look for it right now since I think that probably noone will want it)
For other geeks that want to take this further, my makefile that I used to build the package (I assume you can understand the folder structure and copy & paste the corresponding files where they belong):

@Turris Omnia Team: Would it be possible to enable (at least) the following kernel options at some point in the future?

Especially the cgroups would make docker more reliable. Thanks!

Have fun and enjoy the rest of your day!


I’m not here much but if you’d get stuck, ping and I’ll try to talk you through what I did at least …


A package I would really happy to get is infenslave - did anyone build it already?

@paja: would it be possible to add package ifenslave to repository?

@paja: would be really nice to get that package! :hugs:

What are you trying to do? I am not exactly network guy so I don’t know (or remember) how exactly you can use it. But from my understanding this is BSD type network tool. Linux ip utils should handle that too. Specially if I am not mistaken you want to use ip l set master.

Please find what I actually did here.
Maybe there are other solutions out there but those are rarely documented.
@paja wrote an answer but deleted it before I could read so I don’t know what he had on his mind about that topic.

Hi @pepe & Turris team…

Is there any chance of upgrading the nginx package to the latest upstream version?

The TO version is 1.10, and the latest stable version is 1.14: The upstream version is 1.12:

There are some pretty big changes between 1.10 & 1.12 - that would be a start, but 1.14 might be even better!

Or has someone written up how to install OpenWrt packages on TO? (I know the platform is mvebu, but today, I can’t find it in

You could try directly installing from (v.1.12)

I guess that would work for BASH scripts (e.g. adblock), but for binaries (like nginx)?

1 Like

I used to install adblock that way until Turris team put a current version into TO repo.

This would work because adblock is just BASH scripts. It wont work with nginx because that package would contain compiled binaries…

Hello @dbonnes,

I’m aware of your issue, so I’ve started to learn how can I create Makefiles and how the things works, so I can help my colleagues with packages. :slight_smile:

It’s quite interesting experience, but unfortunately right now nginx will be a little bit complicated to me, so I have created the case to our Gitlab. So colleagues can take a look into it.

If there will be any progress you’d see it on our Gitlab. You can opt-in for notifications.

Would it be possible to update transmission to 2.94 ? Thanks a lot.

thank you for your request.

I’ve created the issue on our Gitlab, where I’ll keep you updated on any progress.

Also for nginx guys I’ve good news, we’ll update in Turris OS 3.10.4.

1 Like

Can you update Nextcloud from version 13 to 14?

Better odds (as in package maintainer awareness than the forum) perhaps by opening an issue in where it gets (or might get) a milestone and progress can be tracked.

Please feature luci-proto-uqmi package: in the next relase.

Hah, they must read this forum:


Yes, we’re reading the forum, but the update for Nextcloud was planned as we’re cooperating with them. Currently, it is updated only in our Nightly branch as we wants to test it and add some tweaks. The thing is that we included Nextcloud update to version 13.0.6 in Turris OS 3.10.6, which we released 11 days ago.

From what we know, Nextcloud developers recommends to update to 14 from 13.0.6 and form this version the update should went very well as it is tested, but from earlier versions, there might be some issues.

1 Like

Would it be possible to add s3fs-fuse to the packages?

I’d like to be able to use the Omnia as an edge cache to Wasabi S3 storage, thanks.