Re: [OpenWrt-Devel] [PATCH, V2] fstools: mount ntfs with ntfs-3g utility if it exist
I’m not seeing where “mount.ntfs-3g” is being set as the program to use... and
should the test for the presence and modes of the program be generic? i.e.
regardless of what type of FS or which program you use to mount it, you’ll want
to test for its presence.
So these are really two independent things.
> On Sep 30, 2018, at 9:04 PM, Rosy Song wrote:
>
> Signed-off-by: Rosy Song
> ---
> block.c | 8 +++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/block.c b/block.c
> index 2651c86..b2cd32b 100644
> --- a/block.c
> +++ b/block.c
> @@ -881,7 +881,13 @@ static int handle_mount(const char *source, const char
> *target,
>size_t mount_opts_len;
>char *mount_opts = NULL, *ptr;
>
> -err = mount(source, target, fstype, m ? m->flags : 0,
> +/* Mount ntfs filesystem with ntfs-3g utility */
> +if (!strcmp(fstype, "ntfs") &&
> +!access("/sbin/mount.ntfs-3g", X_OK)) {
> +err = -1;
> +errno = ENODEV;
> +} else
> +err = mount(source, target, fstype, m ? m->flags : 0,
>(m && m->options) ? m->options : "");
>
>/* Requested file system type is not available in kernel,
> --
> 2.17.0
>
>
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH, V2] fstools: mount ntfs with ntfs-3g utility if it exist
Signed-off-by: Rosy Song
---
block.c | 8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/block.c b/block.c
index 2651c86..b2cd32b 100644
--- a/block.c
+++ b/block.c
@@ -881,7 +881,13 @@ static int handle_mount(const char *source, const char
*target,
size_t mount_opts_len;
char *mount_opts = NULL, *ptr;
- err = mount(source, target, fstype, m ? m->flags : 0,
+ /* Mount ntfs filesystem with ntfs-3g utility */
+ if (!strcmp(fstype, "ntfs") &&
+ !access("/sbin/mount.ntfs-3g", X_OK)) {
+ err = -1;
+ errno = ENODEV;
+ } else
+ err = mount(source, target, fstype, m ? m->flags : 0,
(m && m->options) ? m->options : "");
/* Requested file system type is not available in kernel,
--
2.17.0
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] router unielec U7628-01 won't boot - step to track down the problem ?
i have buied a router from unielec, the second unit , but this time the router , arrived in working perfect condition with the factory firmware (openwrt custom) , when i try to flash the last firmware , won't boot ... i make some test , i hope in the right direction , but now i don't have enough skill to track down the problem. i make a log with the original firmware : https://pastebin.com/Sa2XGiDP after this i write to flash the openwrt 18.06.1 https://pastebin.com/MVsqxpCS the router doesn't boot , all led are off , eth is up but no data come from the router , in the serial consolle if i hit enter , nothings happen then i decide to try the snapshot , from 27 september , https://pastebin.com/wLPNFB9h i obtain [ 1.709386] Unhandled kernel unaligned access[#1]: i try then to make my own snapshot, clone the repo , enable the "target image : ramdisk" , adjust the dtsi to set the serial speed the same as the bootloader compile boot to ram : https://pastebin.com/MzTDc7Ac boot from flash after writing to flash : https://pastebin.com/bGJX4gVR in one of my test (not reported here) i see sometimes , i have an error about root filsystem not set , then i add the filesystem path in the dtsi file , recompile and test boot to ram : https://pastebin.com/rH6s9Dfe boot from flash after writing to flash : https://pastebin.com/FTYuC0k4 if i write to the flash the original bin firmware, all come back ok, the only difference between the two unit is that the first have a breed bootloader this one have u-boot , but the developer , tell me that the firmware they made is the same for both bootloader now: is correct to enable the "target image : ramdisk" to make the test? are they valid as when i flash the firmware? is necessary to set the filesystem path? someone can point me on a more clear (for me) paper about the flash structure , and how it is detected? unfortunately i'm unable to resolve this error, then i need some big help from the comunity , but i can make the test ... if needed the maker grant me the permission to share the bin file , but not the source code about this image ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] RFT: ar71xx/mac80211 update
On 09/26/2018 12:01 AM, Daniel Golle wrote: > On Tue, Sep 25, 2018 at 11:15:14PM +0200, Hauke Mehrtens wrote: >> ... >> With that update I am fine with squashing the mac80211 updates and >> pushing them to OpenWrt master. >> >> I checked the removed patches and could not find these two patches in >> the upstream kernel: >> * >> package/kernel/mac80211/patches/600-23-rt2x00-rt2800mmio-add-a-workaround-for-spurious-TX_F.patch > > Yes, this one should be dropped according to Stanislaw Gruszka, we've > discussed this earlier, but can't spot the thread right now. Ok, I just wanted to make sure this was done by intention and not by mistake. Now I know that this was done by intention. Hauke >> * >> package/kernel/mac80211/patches/367-Revert-ath10k-disable-wake_tx_queue-for-older-device.patch For me it looks ok that this one got removed. Hauke signature.asc Description: OpenPGP digital signature ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 2/3] mpc85xx: kernel 4.14
Am 30.09.18 um 21:45 schrieb Magnus Kroken: Hi Achim On 06.06.2018 23:42, Achim Gottinger wrote: Am 05.06.2018 um 00:09 schrieb Magnus Kroken: Tested-by: Magnus Kroken Works well on my WDR4900v1. I don't use the crypto driver, so can't respond to those changes, but the Wi-Fi radios, ethernet and the basic hardware works fine. Most of your patches haven't shown up in Patchwork though [1]. Not sure if there was an issue with Patchwork when you sent your series, it could also be caused by your mail client malforming the e-mails. You may want to resubmit the series to ensure they are kept track of, with git-send-email if possible. 1: http://patchwork.ozlabs.org/project/openwrt/list/?series=&submitter=74207&state=*&q=&archive=both&delegate= Regards /Magnus Thank you for thes tests and the tips about patchwork. Can be I used the wron numbering for the series because i did not start with 0/3. But I plan to modify the patches in an way that the caam modules are build in for generic/p1020 targets and are disabled only on wdr4900v1 which has no hardware crypto enabled. This way the additional caam module package is not required and the change does not interfere with other subtargets. achim~ Do you have any plans to move forward with your mpc85xx 4.14 patch series? I am still using your patches on top of current master, presently running kernel 4.14.73 on my WDR4900v1, and they work perfectly. Keep in mind that most of your patches did not end up in Patchwork for some reason, so they are not kept track of by anyone. If you find it easier to submit a pull request on Github you can do so here: https://github.com/openwrt/openwrt/pulls /Magnus Hello Magnus, I'm abit short in time this month and may look into it in november again. The caam crypto issues are already fixed upstream, so my modifcations on these are no longer necessary. If you want to push things meanwhile, feel free to do so. :-) Achim~ ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] ar71xx/tiny broken since: "image: use ucert to append signature"
On 09/30/2018 03:53 AM, Daniel Golle wrote:
> Hi!
>
> On Sun, Sep 30, 2018 at 12:27:07AM +0200, Hauke Mehrtens wrote:
>> Hi,
>>
>> The build of the ar71xx/tiny subtarget is broken since this commit:
>> https://git.openwrt.org/848b455d2e9441361f6e010f9b95ab8a7dccbae1
>> see here for the error message in build bot:
>> http://phase1.builds.lede-project.org/builders/ar71xx%2Ftiny
>>
>> When I revert the following commits it builds again:
>> https://git.openwrt.org/ec78f03de589adc9bd47a02d723d7054510601dd
>> https://git.openwrt.org/848b455d2e9441361f6e010f9b95ab8a7dccbae1
>
> Very weird indeed...
>
>>
>>
>> It fails for me like this:
>>
>> /home/hauke/openwrt/lede/staging_dir/host/bin/lzma e
>> /home/hauke/openwrt/lede/build_dir/target-mips_24kc_musl/linux-ar71xx_tiny/tl-wa850re-v2-kernel.bin
>> -lc1 -lp2 -pb2
>> /home/hauke/openwrt/lede/build_dir/target-mips_24kc_musl/linux-ar71xx_tiny/tl-wa850re-v2-kernel.bin.new
>> /home/hauke/openwrt/lede/staging_dir/host/bin/mktplinkfw -c -H
>> 0x0852 -W 0 -L 0x8006 -E 0x8006 -m 1 -N "OpenWrt" -V
>> r8207-99e1a12fd0 -k
>> /home/hauke/openwrt/lede/build_dir/target-mips_24kc_musl/linux-ar71xx_tiny/tl-wa850re-v2-kernel.bin
>> -o
>> /home/hauke/openwrt/lede/build_dir/target-mips_24kc_musl/linux-ar71xx_tiny/tl-wa850re-v2-kernel.bin.new
>>
>> [mktplinkfw] firmware file
>> "/home/hauke/openwrt/lede/build_dir/target-mips_24kc_musl/linux-ar71xx_tiny/tl-wa850re-v2-kernel.bin.new"
>> completed
>> [ -f
>> /home/hauke/openwrt/lede/build_dir/target-mips_24kc_musl/linux-ar71xx_tiny/tl-wa850re-v2-kernel.bin
>> -a -f
>> /home/hauke/openwrt/lede/build_dir/target-mips_24kc_musl/linux-ar71xx_tiny/root.squashfs
>> ]
>> dd
>> if=/home/hauke/openwrt/lede/build_dir/target-mips_24kc_musl/linux-ar71xx_tiny/root.squashfs
>> /home/hauke/openwrt/lede/build_dir/target-mips_24kc_musl/linux-ar71xx_tiny/tmp/openwrt-ar71xx-tiny-tl-wa850re-v2-squashfs-sysupgrade.bin
>> 5495+1 records in
>> 5495+1 records out
>> 2813744 bytes (2.8 MB, 2.7 MiB) copied, 0.00989007 s, 285 MB/s
>> /home/hauke/openwrt/lede/staging_dir/host/bin/tplink-safeloader -B
>> TLWA850REV2 -V r8207-99e1a12fd0 -k
>> /home/hauke/openwrt/lede/build_dir/target-mips_24kc_musl/linux-ar71xx_tiny/tl-wa850re-v2-kernel.bin
>> -r
>> /home/hauke/openwrt/lede/build_dir/target-mips_24kc_musl/linux-ar71xx_tiny/tmp/openwrt-ar71xx-tiny-tl-wa850re-v2-squashfs-sysupgrade.bin
>> -o
>> /home/hauke/openwrt/lede/build_dir/target-mips_24kc_musl/linux-ar71xx_tiny/tmp/openwrt-ar71xx-tiny-tl-wa850re-v2-squashfs-sysupgrade.bin.new
>> -j -S && mv
>> /home/hauke/openwrt/lede/build_dir/target-mips_24kc_musl/linux-ar71xx_tiny/tmp/openwrt-ar71xx-tiny-tl-wa850re-v2-squashfs-sysupgrade.bin.new
>> /home/hauke/openwrt/lede/build_dir/target-mips_24kc_musl/linux-ar71xx_tiny/tmp/openwrt-ar71xx-tiny-tl-wa850re-v2-squashfs-sysupgrade.bin
>> || rm -f
>> /home/hauke/openwrt/lede/build_dir/target-mips_24kc_musl/linux-ar71xx_tiny/tmp/openwrt-ar71xx-tiny-tl-wa850re-v2-squashfs-sysupgrade.bin
>> file-system partition too big (more than 2359296 bytes): Success
> ^^
>
>> [ ! -s "/home/hauke/openwrt/lede/key-build" -o ! -s
>> "/home/hauke/openwrt/lede/key-build.ucert" ] || { cp
>> "/home/hauke/openwrt/lede/key-build.ucert"
>> "/home/hauke/openwrt/lede/build_dir/target-mips_24kc_musl/linux-ar71xx_tiny/tmp/openwrt-ar71xx-tiny-tl-wa850re-v2-squashfs-sysupgrade.bin.ucert"
>> ; usign -S -m
>> "/home/hauke/openwrt/lede/build_dir/target-mips_24kc_musl/linux-ar71xx_tiny/tmp/openwrt-ar71xx-tiny-tl-wa850re-v2-squashfs-sysupgrade.bin"
>> -s "/home/hauke/openwrt/lede/key-build" -x
>> "/home/hauke/openwrt/lede/build_dir/target-mips_24kc_musl/linux-ar71xx_tiny/tmp/openwrt-ar71xx-tiny-tl-wa850re-v2-squashfs-sysupgrade.bin.sig"
>> ; ucert -A -c
>> "/home/hauke/openwrt/lede/build_dir/target-mips_24kc_musl/linux-ar71xx_tiny/tmp/openwrt-ar71xx-tiny-tl-wa850re-v2-squashfs-sysupgrade.bin.ucert"
>> -x
>> "/home/hauke/openwrt/lede/build_dir/target-mips_24kc_musl/linux-ar71xx_tiny/tmp/openwrt-ar71xx-tiny-tl-wa850re-v2-squashfs-sysupgrade.bin.sig"
>> ; fwtool -S
>> "/home/hauke/openwrt/lede/build_dir/target-mips_24kc_musl/linux-ar71xx_tiny/tmp/openwrt-ar71xx-tiny-tl-wa850re-v2-squashfs-sysupgrade.bin.ucert"
>> "/home/hauke/openwrt/lede/build_dir/target-mips_24kc_musl/linux-ar71xx_tiny/tmp/openwrt-ar71xx-tiny-tl-wa850re-v2-squashfs-sysupgrade.bin"
>> ; }
>> Cannot open message file: No such file or directory
>
> Looks like usign complaining that supposedly
> "/home/hauke/openwrt/lede/build_dir/target-mips_24kc_musl/linux-ar71xx_tiny/tmp/openwrt-ar71xx-tiny-tl-wa850re-v2-squashfs-sysupgrade.bin"
> cannot be found. Maybe because of the image size warning above?
Yes probably this is caused by the size.
We had the problem that the size caused some build problems multiple
times. Should we really deactivate the boards manually which are too big
or can we just make the build not create images for this board and not
fail in this case.
I
Re: [OpenWrt-Devel] [PATCH] fstools: mount ntfs with ntfs-3g utility if it exists
Comments inline
> On Sep 29, 2018, at 9:04 PM, Rosy Song wrote:
>
> From: Rosy Song
> Subject: [OpenWrt-Devel] [PATCH] fstools: mount ntfs with ntfs-3g utility if
> it exists
>
> This patch can mount ntfs with fuseblk fs type and make the deivces to be
> mounted writable.
>
> --- a/block.c
> +++ b/block.c
> @@ -881,7 +881,13 @@ static int handle_mount(const char *sour
> size_t mount_opts_len;
> char *mount_opts = NULL, *ptr;
>
> - err = mount(source, target, fstype, m ? m->flags : 0,
> + if (!strncmp(fstype, "ntfs", strlen(fstype)) &&
How is this any different from !strcmp(fstype, “ntfs”) ?
> + !access("/sbin/mount.ntfs-3g", X_OK)) {
> + // mount ntfs filesystem with ntfs-3g utility
> + err = -1;
> + errno = ENODEV;
> + } else
> + err = mount(source, target, fstype, m ? m->flags : 0,
> (m && m->options) ? m->options : "");
>
> /* Requested file system type is not available in kernel,
>
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 2/3] mpc85xx: kernel 4.14
Hi Achim On 06.06.2018 23:42, Achim Gottinger wrote: Am 05.06.2018 um 00:09 schrieb Magnus Kroken: Tested-by: Magnus Kroken Works well on my WDR4900v1. I don't use the crypto driver, so can't respond to those changes, but the Wi-Fi radios, ethernet and the basic hardware works fine. Most of your patches haven't shown up in Patchwork though [1]. Not sure if there was an issue with Patchwork when you sent your series, it could also be caused by your mail client malforming the e-mails. You may want to resubmit the series to ensure they are kept track of, with git-send-email if possible. 1: http://patchwork.ozlabs.org/project/openwrt/list/?series=&submitter=74207&state=*&q=&archive=both&delegate= Regards /Magnus Thank you for thes tests and the tips about patchwork. Can be I used the wron numbering for the series because i did not start with 0/3. But I plan to modify the patches in an way that the caam modules are build in for generic/p1020 targets and are disabled only on wdr4900v1 which has no hardware crypto enabled. This way the additional caam module package is not required and the change does not interfere with other subtargets. achim~ Do you have any plans to move forward with your mpc85xx 4.14 patch series? I am still using your patches on top of current master, presently running kernel 4.14.73 on my WDR4900v1, and they work perfectly. Keep in mind that most of your patches did not end up in Patchwork for some reason, so they are not kept track of by anyone. If you find it easier to submit a pull request on Github you can do so here: https://github.com/openwrt/openwrt/pulls /Magnus ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] OpenWrt 19.01 plans
On Sun, Sep 30, 2018 at 12:53 AM Stefan Lippers-Hollmann wrote: > > Hi > > On 2018-09-29, Torbjorn Jansson wrote: > > checkbox for hw offloading shows up for a fraction of a second when page is > > loaded but then it disappears. > > so i take it luci removes it dynamically or something at page load. > > flow-offloading has only beenbackported to kernel 4.14, if your target > is still on an older kernel (e.g. ar71xx is still on kernel 4.9), it > isn't available. In release 19.01 targets will be moved to kernel 4.14 including ar71xx see [1]. Currently ar71xx has already support for kernel 4.14 [2] but the default version is 4.9 atm [1] http://lists.infradead.org/pipermail/openwrt-adm/2018-August/000863.html [2] https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=318e19ba6755105bb6cc19937d8fff26cbd2cc6f Hans > > Regards > Stefan Lippers-Hollmann > > ___ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] fstools: mount ntfs with ntfs-3g utility if it exists
On Sun, Sep 30, 2018 at 5:05 AM Rosy Song wrote:
>
> From: Rosy Song
> Subject: [OpenWrt-Devel] [PATCH] fstools: mount ntfs with ntfs-3g utility if
> it exists
>
> This patch can mount ntfs with fuseblk fs type and make the deivces to be
> mounted writable.
Did you create the patch via git format-patch ?
The patch is also missing a SoB; please have a look at
https://openwrt.org/submitting-patches
Hans
>
> --- a/block.c
> +++ b/block.c
> @@ -881,7 +881,13 @@ static int handle_mount(const char *sour
> size_t mount_opts_len;
> char *mount_opts = NULL, *ptr;
>
> - err = mount(source, target, fstype, m ? m->flags : 0,
> + if (!strncmp(fstype, "ntfs", strlen(fstype)) &&
> + !access("/sbin/mount.ntfs-3g", X_OK)) {
> + // mount ntfs filesystem with ntfs-3g utility
> + err = -1;
> + errno = ENODEV;
> + } else
> + err = mount(source, target, fstype, m ? m->flags : 0,
> (m && m->options) ? m->options : "");
>
> /* Requested file system type is not available in kernel,
>
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] running docker on openwrt?
On 2018-09-30 17:18, Daniel Golle wrote: On Sun, Sep 30, 2018 at 04:52:04PM +0200, Torbjorn Jansson wrote: On 2018-09-30 16:21, Daniel Golle wrote: On Sun, Sep 30, 2018 at 02:18:54PM +0200, Torbjorn Jansson wrote: On 2018-09-30 13:59, Daniel Golle wrote: On Sun, Sep 30, 2018 at 12:21:12PM +0200, Torbjorn Jansson wrote: Hello. a question, is it possible to run docker on openwrt? reason for asking is that i got a raspberrypi running openwrt and it got plenty of storage space and is mostly sitting idle so if i can run docker on it i might be able to consolidate some of the other pis i have for various purposes. i know you can do it the other way around, running openwrt in a docker instance on a regular computer but can you get docker itself to run under openwrt? ideas, suggestions? Just use LXC, that works well on OpenWrt, I'm using that to run various containers running Debian and OpenWrt on top of OpenWrt. (but you need to compile it yourself because many of the kernel options needed for containers aren't enabled by default) Docker didn't attract a lot of interest because it is x86_64 and ARM-only, so 80% of OpenWrt-supported devices aren't supported by Docker which doesn't provide images for MIPS-like CPUs. However, now that Golang has been added to the packages feed we could package Docker at least for the platforms supported by it... ok, i see. i've never tried lxc and i think docker also needs some extra kernel config options for it to work. i ran the script from: https://raw.githubusercontent.com/docker/docker/master/contrib/check-config.sh on one of my boxes and it complained about: - CONFIG_NAMESPACES: missing - CONFIG_NET_NS: missing - CONFIG_PID_NS: missing - CONFIG_IPC_NS: missing - CONFIG_UTS_NS: missing - CONFIG_CGROUPS: missing - CONFIG_CGROUP_CPUACCT: missing - CONFIG_CGROUP_DEVICE: missing - CONFIG_CGROUP_FREEZER: missing - CONFIG_CGROUP_SCHED: missing - CONFIG_CPUSETS: missing - CONFIG_MEMCG: missing - CONFIG_NETFILTER_XT_MATCH_IPVS: missing - CONFIG_POSIX_MQUEUE: missing and then there were a bunch of optional features also missing. For now the binary distribution doesn't have all those kernel features enabled. You need to compile from source and make sure that CONFIG_LXC_KERNEL_OPTIONS is set, this selects all the kernel options needed to run containers. i see, so a package can modify the kernel options and enable needed features. that's quite handy, i didn't know that. what i tried to do was to run: make kernel_menuconfig CONFIG_TARGET=subtarget and then pick the right options myself and then check it with: git diff target/linux/ the diff looked good but the resulting image did not include my extra kernel config options for some reason and in don't understand why. This is not the intended ue of make kernel_menuconfig, that's why... i assumed the stuff in target/linux/brcm2708/bcm2710/config-4.9 was going to be used as a default template or something but maybe other config options is overriding it. Exactly. The kernel options which are also listed in OpenWrt's .config always override the target-specific selection made by kernel_menuconfig. i'm no expert on the build system (yet?) so any pointers for manually adding a few extra config options for testing purposes would be nice. Just use the regular menuconfig's options mentioned above, all the cgroups and namespace stuff is listed there as well. ok, my idea was to add a few extra options too. so i guess i'll have to figure out how to make a small package of my own that adds all the kernel options, like the lxc one you pointed to. is it safe to assume that the build system will take care of dependencies in the kernel config? or do i have to figure that out myself and make sure i also add any kernel config dependencies? Luka Perkov (@lperkov )and Marko Ratkaj (@ratkaj) can supposedly tell you more about the LXC integration in OpenWrt. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] running docker on openwrt?
On Sun, Sep 30, 2018 at 04:52:04PM +0200, Torbjorn Jansson wrote: > On 2018-09-30 16:21, Daniel Golle wrote: > > On Sun, Sep 30, 2018 at 02:18:54PM +0200, Torbjorn Jansson wrote: > > > On 2018-09-30 13:59, Daniel Golle wrote: > > > > On Sun, Sep 30, 2018 at 12:21:12PM +0200, Torbjorn Jansson wrote: > > > > > Hello. > > > > > > > > > > a question, is it possible to run docker on openwrt? > > > > > reason for asking is that i got a raspberrypi running openwrt and it > > > > > got > > > > > plenty of storage space and is mostly sitting idle so if i can run > > > > > docker on > > > > > it i might be able to consolidate some of the other pis i have for > > > > > various > > > > > purposes. > > > > > > > > > > i know you can do it the other way around, running openwrt in a docker > > > > > instance on a regular computer but can you get docker itself to run > > > > > under > > > > > openwrt? > > > > > > > > > > ideas, suggestions? > > > > > > > > Just use LXC, that works well on OpenWrt, I'm using that to run various > > > > containers running Debian and OpenWrt on top of OpenWrt. > > > > (but you need to compile it yourself because many of the kernel options > > > > needed for containers aren't enabled by default) > > > > > > > > Docker didn't attract a lot of interest because it is x86_64 and > > > > ARM-only, so 80% of OpenWrt-supported devices aren't supported by > > > > Docker which doesn't provide images for MIPS-like CPUs. > > > > > > > > However, now that Golang has been added to the packages feed we could > > > > package Docker at least for the platforms supported by it... > > > > > > > > > > ok, i see. > > > i've never tried lxc and i think docker also needs some extra kernel > > > config > > > options for it to work. > > > > > > i ran the script from: > > > https://raw.githubusercontent.com/docker/docker/master/contrib/check-config.sh > > > on one of my boxes and it complained about: > > > - CONFIG_NAMESPACES: missing > > > - CONFIG_NET_NS: missing > > > - CONFIG_PID_NS: missing > > > - CONFIG_IPC_NS: missing > > > - CONFIG_UTS_NS: missing > > > - CONFIG_CGROUPS: missing > > > - CONFIG_CGROUP_CPUACCT: missing > > > - CONFIG_CGROUP_DEVICE: missing > > > - CONFIG_CGROUP_FREEZER: missing > > > - CONFIG_CGROUP_SCHED: missing > > > - CONFIG_CPUSETS: missing > > > - CONFIG_MEMCG: missing > > > - CONFIG_NETFILTER_XT_MATCH_IPVS: missing > > > - CONFIG_POSIX_MQUEUE: missing > > > > > > and then there were a bunch of optional features also missing. > > > > For now the binary distribution doesn't have all those kernel features > > enabled. You need to compile from source and make sure that > > CONFIG_LXC_KERNEL_OPTIONS is set, this selects all the kernel options > > needed to run containers. > > > > i see, so a package can modify the kernel options and enable needed features. > that's quite handy, i didn't know that. > > what i tried to do was to run: > make kernel_menuconfig CONFIG_TARGET=subtarget > and then pick the right options myself and then check it with: > git diff target/linux/ > > the diff looked good but the resulting image did not include my extra kernel > config options for some reason and in don't understand why. This is not the intended ue of make kernel_menuconfig, that's why... > i assumed the stuff in target/linux/brcm2708/bcm2710/config-4.9 was going to > be used as a default template or something but maybe other config options is > overriding it. Exactly. The kernel options which are also listed in OpenWrt's .config always override the target-specific selection made by kernel_menuconfig. > > i'm no expert on the build system (yet?) so any pointers for manually adding > a few extra config options for testing purposes would be nice. > Just use the regular menuconfig's options mentioned above, all the cgroups and namespace stuff is listed there as well. Luka Perkov (@lperkov )and Marko Ratkaj (@ratkaj) can supposedly tell you more about the LXC integration in OpenWrt. Cheers Daniel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] running docker on openwrt?
On 2018-09-30 16:21, Daniel Golle wrote: On Sun, Sep 30, 2018 at 02:18:54PM +0200, Torbjorn Jansson wrote: On 2018-09-30 13:59, Daniel Golle wrote: On Sun, Sep 30, 2018 at 12:21:12PM +0200, Torbjorn Jansson wrote: Hello. a question, is it possible to run docker on openwrt? reason for asking is that i got a raspberrypi running openwrt and it got plenty of storage space and is mostly sitting idle so if i can run docker on it i might be able to consolidate some of the other pis i have for various purposes. i know you can do it the other way around, running openwrt in a docker instance on a regular computer but can you get docker itself to run under openwrt? ideas, suggestions? Just use LXC, that works well on OpenWrt, I'm using that to run various containers running Debian and OpenWrt on top of OpenWrt. (but you need to compile it yourself because many of the kernel options needed for containers aren't enabled by default) Docker didn't attract a lot of interest because it is x86_64 and ARM-only, so 80% of OpenWrt-supported devices aren't supported by Docker which doesn't provide images for MIPS-like CPUs. However, now that Golang has been added to the packages feed we could package Docker at least for the platforms supported by it... ok, i see. i've never tried lxc and i think docker also needs some extra kernel config options for it to work. i ran the script from: https://raw.githubusercontent.com/docker/docker/master/contrib/check-config.sh on one of my boxes and it complained about: - CONFIG_NAMESPACES: missing - CONFIG_NET_NS: missing - CONFIG_PID_NS: missing - CONFIG_IPC_NS: missing - CONFIG_UTS_NS: missing - CONFIG_CGROUPS: missing - CONFIG_CGROUP_CPUACCT: missing - CONFIG_CGROUP_DEVICE: missing - CONFIG_CGROUP_FREEZER: missing - CONFIG_CGROUP_SCHED: missing - CONFIG_CPUSETS: missing - CONFIG_MEMCG: missing - CONFIG_NETFILTER_XT_MATCH_IPVS: missing - CONFIG_POSIX_MQUEUE: missing and then there were a bunch of optional features also missing. For now the binary distribution doesn't have all those kernel features enabled. You need to compile from source and make sure that CONFIG_LXC_KERNEL_OPTIONS is set, this selects all the kernel options needed to run containers. i see, so a package can modify the kernel options and enable needed features. that's quite handy, i didn't know that. what i tried to do was to run: make kernel_menuconfig CONFIG_TARGET=subtarget and then pick the right options myself and then check it with: git diff target/linux/ the diff looked good but the resulting image did not include my extra kernel config options for some reason and in don't understand why. i assumed the stuff in target/linux/brcm2708/bcm2710/config-4.9 was going to be used as a default template or something but maybe other config options is overriding it. i'm no expert on the build system (yet?) so any pointers for manually adding a few extra config options for testing purposes would be nice. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] running docker on openwrt?
On Sun, Sep 30, 2018 at 02:18:54PM +0200, Torbjorn Jansson wrote: > On 2018-09-30 13:59, Daniel Golle wrote: > > On Sun, Sep 30, 2018 at 12:21:12PM +0200, Torbjorn Jansson wrote: > > > Hello. > > > > > > a question, is it possible to run docker on openwrt? > > > reason for asking is that i got a raspberrypi running openwrt and it got > > > plenty of storage space and is mostly sitting idle so if i can run docker > > > on > > > it i might be able to consolidate some of the other pis i have for various > > > purposes. > > > > > > i know you can do it the other way around, running openwrt in a docker > > > instance on a regular computer but can you get docker itself to run under > > > openwrt? > > > > > > ideas, suggestions? > > > > Just use LXC, that works well on OpenWrt, I'm using that to run various > > containers running Debian and OpenWrt on top of OpenWrt. > > (but you need to compile it yourself because many of the kernel options > > needed for containers aren't enabled by default) > > > > Docker didn't attract a lot of interest because it is x86_64 and > > ARM-only, so 80% of OpenWrt-supported devices aren't supported by > > Docker which doesn't provide images for MIPS-like CPUs. > > > > However, now that Golang has been added to the packages feed we could > > package Docker at least for the platforms supported by it... > > > > ok, i see. > i've never tried lxc and i think docker also needs some extra kernel config > options for it to work. > > i ran the script from: > https://raw.githubusercontent.com/docker/docker/master/contrib/check-config.sh > on one of my boxes and it complained about: > - CONFIG_NAMESPACES: missing > - CONFIG_NET_NS: missing > - CONFIG_PID_NS: missing > - CONFIG_IPC_NS: missing > - CONFIG_UTS_NS: missing > - CONFIG_CGROUPS: missing > - CONFIG_CGROUP_CPUACCT: missing > - CONFIG_CGROUP_DEVICE: missing > - CONFIG_CGROUP_FREEZER: missing > - CONFIG_CGROUP_SCHED: missing > - CONFIG_CPUSETS: missing > - CONFIG_MEMCG: missing > - CONFIG_NETFILTER_XT_MATCH_IPVS: missing > - CONFIG_POSIX_MQUEUE: missing > > and then there were a bunch of optional features also missing. For now the binary distribution doesn't have all those kernel features enabled. You need to compile from source and make sure that CONFIG_LXC_KERNEL_OPTIONS is set, this selects all the kernel options needed to run containers. > > i'm for any way of running containers on a openwrt image, like my pis > > then i should be able to run some of my stuff as a container and i don't > have to worry too much about various packages and so on since i can run for > example a debian container plus i could likely consolidated my stuff to just > one box instead of 3 separate. > plus one of the programs i need is very picky about having exactly the right > libraries and versions of them. > > ___ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] running docker on openwrt?
On 2018-09-30 13:59, Daniel Golle wrote: On Sun, Sep 30, 2018 at 12:21:12PM +0200, Torbjorn Jansson wrote: Hello. a question, is it possible to run docker on openwrt? reason for asking is that i got a raspberrypi running openwrt and it got plenty of storage space and is mostly sitting idle so if i can run docker on it i might be able to consolidate some of the other pis i have for various purposes. i know you can do it the other way around, running openwrt in a docker instance on a regular computer but can you get docker itself to run under openwrt? ideas, suggestions? Just use LXC, that works well on OpenWrt, I'm using that to run various containers running Debian and OpenWrt on top of OpenWrt. (but you need to compile it yourself because many of the kernel options needed for containers aren't enabled by default) Docker didn't attract a lot of interest because it is x86_64 and ARM-only, so 80% of OpenWrt-supported devices aren't supported by Docker which doesn't provide images for MIPS-like CPUs. However, now that Golang has been added to the packages feed we could package Docker at least for the platforms supported by it... ok, i see. i've never tried lxc and i think docker also needs some extra kernel config options for it to work. i ran the script from: https://raw.githubusercontent.com/docker/docker/master/contrib/check-config.sh on one of my boxes and it complained about: - CONFIG_NAMESPACES: missing - CONFIG_NET_NS: missing - CONFIG_PID_NS: missing - CONFIG_IPC_NS: missing - CONFIG_UTS_NS: missing - CONFIG_CGROUPS: missing - CONFIG_CGROUP_CPUACCT: missing - CONFIG_CGROUP_DEVICE: missing - CONFIG_CGROUP_FREEZER: missing - CONFIG_CGROUP_SCHED: missing - CONFIG_CPUSETS: missing - CONFIG_MEMCG: missing - CONFIG_NETFILTER_XT_MATCH_IPVS: missing - CONFIG_POSIX_MQUEUE: missing and then there were a bunch of optional features also missing. i'm for any way of running containers on a openwrt image, like my pis then i should be able to run some of my stuff as a container and i don't have to worry too much about various packages and so on since i can run for example a debian container plus i could likely consolidated my stuff to just one box instead of 3 separate. plus one of the programs i need is very picky about having exactly the right libraries and versions of them. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] running docker on openwrt?
On Sun, Sep 30, 2018 at 12:21:12PM +0200, Torbjorn Jansson wrote: > Hello. > > a question, is it possible to run docker on openwrt? > reason for asking is that i got a raspberrypi running openwrt and it got > plenty of storage space and is mostly sitting idle so if i can run docker on > it i might be able to consolidate some of the other pis i have for various > purposes. > > i know you can do it the other way around, running openwrt in a docker > instance on a regular computer but can you get docker itself to run under > openwrt? > > ideas, suggestions? Just use LXC, that works well on OpenWrt, I'm using that to run various containers running Debian and OpenWrt on top of OpenWrt. (but you need to compile it yourself because many of the kernel options needed for containers aren't enabled by default) Docker didn't attract a lot of interest because it is x86_64 and ARM-only, so 80% of OpenWrt-supported devices aren't supported by Docker which doesn't provide images for MIPS-like CPUs. However, now that Golang has been added to the packages feed we could package Docker at least for the platforms supported by it... ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] running docker on openwrt?
Hello. a question, is it possible to run docker on openwrt? reason for asking is that i got a raspberrypi running openwrt and it got plenty of storage space and is mostly sitting idle so if i can run docker on it i might be able to consolidate some of the other pis i have for various purposes. i know you can do it the other way around, running openwrt in a docker instance on a regular computer but can you get docker itself to run under openwrt? ideas, suggestions? ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
