Code Monkey home page Code Monkey logo

docker's Introduction

OpenWrt logo

OpenWrt Project is a Linux operating system targeting embedded devices. Instead of trying to create a single, static firmware, OpenWrt provides a fully writable filesystem with package management. This frees you from the application selection and configuration provided by the vendor and allows you to customize the device through the use of packages to suit any application. For developers, OpenWrt is the framework to build an application without having to build a complete firmware around it; for users this means the ability for full customization, to use the device in ways never envisioned.

Sunshine!

Download

Built firmware images are available for many architectures and come with a package selection to be used as WiFi home router. To quickly find a factory image usable to migrate from a vendor stock firmware to OpenWrt, try the Firmware Selector.

If your device is supported, please follow the Info link to see install instructions or consult the support resources listed below.

An advanced user may require additional or specific package. (Toolchain, SDK, ...) For everything else than simple firmware download, try the wiki download page:

Development

To build your own firmware you need a GNU/Linux, BSD or macOS system (case sensitive filesystem required). Cygwin is unsupported because of the lack of a case sensitive file system.

Requirements

You need the following tools to compile OpenWrt, the package names vary between distributions. A complete list with distribution specific packages is found in the Build System Setup documentation.

binutils bzip2 diff find flex gawk gcc-6+ getopt grep install libc-dev libz-dev
make4.1+ perl python3.7+ rsync subversion unzip which

Quickstart

  1. Run ./scripts/feeds update -a to obtain all the latest package definitions defined in feeds.conf / feeds.conf.default

  2. Run ./scripts/feeds install -a to install symlinks for all obtained packages into package/feeds/

  3. Run make menuconfig to select your preferred configuration for the toolchain, target system & firmware packages.

  4. Run make to build your firmware. This will download all sources, build the cross-compile toolchain and then cross-compile the GNU/Linux kernel & all chosen applications for your target system.

Related Repositories

The main repository uses multiple sub-repositories to manage packages of different categories. All packages are installed via the OpenWrt package manager called opkg. If you're looking to develop the web interface or port packages to OpenWrt, please find the fitting repository below.

  • LuCI Web Interface: Modern and modular interface to control the device via a web browser.

  • OpenWrt Packages: Community repository of ported packages.

  • OpenWrt Routing: Packages specifically focused on (mesh) routing.

  • OpenWrt Video: Packages specifically focused on display servers and clients (Xorg and Wayland).

Support Information

For a list of supported devices see the OpenWrt Hardware Database

Documentation

Support Community

  • Forum: For usage, projects, discussions and hardware advise.
  • Support Chat: Channel #openwrt on oftc.net.

Developer Community

License

OpenWrt is licensed under GPL-2.0

docker's People

Contributors

aparcar avatar bam80 avatar bkpepe avatar bwoodsend avatar dependabot[bot] avatar fakoor avatar jefferyto avatar jonglezb avatar oxr463 avatar polynomialdivision avatar starsbysea avatar ynezz avatar zaoqi avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

docker's Issues

Provide a guide for using the image

Hi, I found this repo and the docker image but there are no real instructions provided for running it.

Sure there is: docker run --rm -it openwrtorg/rootfs but this does not help as it does not get the container running properly:

Failed to resize receive buffer: Operation not permitted
/etc/preinit: line 5: can't create /sys/devices/system/cpu/microcode/reload: Read-only file system
ip: RTNETLINK answers: Operation not permitted
Press the [f] key and hit [enter] to enter failsafe mode
Press the [1], [2], [3] or [4] key and hit [enter] to select the debug level
ip: can't send flush request: Operation not permitted
ip: SIOCSIFFLAGS: Operation not permitted
Please press Enter to activate this console.

What caps does one need to add to get this running?
Does it need to be in privileged mode?
What devices need to be mounted into the container?
How can the webinterface be launched?

I want to use this image for having a router on my home server in docker for my home network.

Thank you and all the best!

run as network client without extra privileges

Hi, Im attempting to use OpenWRT as a lightweight server rather than a router. I don't think I should need NET_ADMIN or other privileges to run the OpenWRT docker service as a network client. Any direction?

$ docker run --rm -it --name ow-dev td7x/openwrt /bin/ash
Failed to resize receive buffer: Operation not permitted
/etc/preinit: line 6: can't create /sys/devices/system/cpu/microcode/reload: Read-only file system
ip: RTNETLINK answers: Operation not permitted
Press the [f] key and hit [enter] to enter failsafe mode
Press the [1], [2], [3] or [4] key and hit [enter] to select the debug level
ip: can't send flush request: Operation not permitted
ip: SIOCSIFFLAGS: Operation not permitted

/etc/config/dhcp

...
config dhcp lan
  option interface	lan
  option ignore	1

/etc/config/firewall

config defaults
        option syn_flood '1'
        option input 'ACCEPT'
        option output 'ACCEPT'
        option forward 'REJECT'

config include
        option path '/etc/firewall.user'

config zone
        option name 'lan'
        option input 'ACCEPT'
        option output 'ACCEPT'
        option forward 'ACCEPT'
        option network 'lan'

/etc/config/network

config interface 'loopback'
    option ifname 'lo'
    option proto 'static'
    option ipaddr '127.0.0.1'
    option netmask '255.0.0.0'

config interface 'lan'
    option ifname 'eth0'
    option proto 'dhcp'

I also get the following in the build:

validation failed
Failed to connect to ubus
Failed to connect to ubus
Warning: Failed to connect to ubus
Warning: Unable to locate ipset utility, disabling ipset support
Warning: Section @zone[0] (lan) cannot resolve device of network 'lan'
Warning: Section @zone[1] (wan) cannot resolve device of network 'wan'
Warning: Section @zone[1] (wan) cannot resolve device of network 'wan6'
 * Set tcp_ecn to off
   ! Unable to write value: Read-only file system
 * Set tcp_syncookies to on
   ! Unable to write value: Read-only file system
 * Set tcp_window_scaling to on
   ! Unable to write value: Read-only file system
 * Running script '/etc/firewall.user'
Failed to connect to ubus
Failed to connect to ubus

Dockerfile

Unable to use docker images on aarch64

I'm not sure what i'm doing wrong, but it looks like even the tags like aarch64_generic-openwrt-21.02 expect to be ran on an amd64 host. Are there any images that will run an aarch64 OS?

I'm trying to use the SDK image

kmodloader: no module folders for kernel version 6.2.2-arch1-1 found

I have two openwrt containers with the same version. After upgraded and reboot arch linux through pacman -Syu, this errors occurs in dmesg in both two containers.

On container works seems fine,but the other container contstantly get a connection refused error in luci web page and also traffics go through this container get lost periodically(about 4s).

Any guys have met this before? I can supply more logs if needed.

Environment:

  • host arch linux(kernel 6.2.2-arch1-1)
  • openwrtorg/rootfs:x86-64-22.03.3

docker interface eth0 has no ip when run with --privilege flag

When I execute docker run command, it has below impacts
Without privileged flag -- ($ docker run -itd openwrtorg/rootfs:x86-64)
Internet is accessible on container
Ip was assigned to docker eth0 interface
With privileged flag -- ($ docker run -itd --privileged openwrtorg/rootfs:x86-64)
Internet not accessible on container
no IP attached to docker eth0 interface, but IP is visible in inspect command output

With --privileged flag we have root privileges but in our case IP is not attached to eth0 primary docker interface.
I just wanna confirm why this strange behavior is being observed.

Thanks
keshav

docker cant run openwrt 1806.4 rootfs.tar.gz

hi
I am jack from china shanghai,I am new for docker ,i want run openwrt 1806.4 rootfs as a image of docker.

I run this cmd:
`
docker import openwrt-x86-64-generic-rootfs.tar.gz
docker run -d --name='op3' c4d3107679c2 /sbin/init #docker start ok,but run ps find uhcpc uhttpd netifd etc.. is not running!

docker run -d --cap-add=NET_ADMIN --name='op3' c4d3107679c2 /sbin/init #openwrt running fine,all important process working!

`
I find @zoobab(http://www.zoobab.com/docker-openwrt-image) image(openwrt version is AA too old) work fine,how??
I want to build a openwrt 1806.4 rootfs,whick running in docker no need net_admin or privileged,pls help!

thanks very much!!

example for gitlab-ci

I am looking for an example how to use the image-builder docker image in a GitLab CI/CD pipeline.
Could anyone post one or add a link/pointer here? Thanks a lot.

Docker Image rootfs under Docker Desktop 2.2 on top of WSL 2.0

OpenWRT container is running but not available. - see attached log
OpenWrtDocker

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
2591ec860c65 openwrtorg/rootfs "/sbin/init" 32 minutes ago Up 32 minutes 22/tcp, 80/tcp, 443/tcp relaxed_cartwright

ping 127.17.02
Pinging 127.17.0.2 with 32 bytes of data:
Reply from 127.17.0.2: bytes=32 time<1ms TTL=128
But
PS C:\WINDOWS\system32> docker inspect 2591ec860c65 > OpnwrtInspect.txt
PS C:\WINDOWS\system32> ssh 127.17.02
ssh: connect to host 127.17.02 port 22: Connection refused

USB and WiFi path trough is supported by WSL 2.0, so
Expected:
It's possible to ssh into OpenWRT container
I have exactly the same issue when I'm trying to ssh into my Router from my Windows, both cmd and WSL 2.0 console.
USB OpenWRT networking can be tested using OpenWRT container
It can be useful both for local testing and regular cloud-based development pipeline

Building a 19.07 firmware

Can you clarify in the readme how to make a 19.07 firmware? I just tried it the image builder is from master.

Building `libnl` with the sdk fails

Hi,

we tried using the sdk container to build libnl. We tried different versions: latest, mvebu-cortexa9-22.03.3, mvebu-cortexa9-22.03.4andmvebu-cortexa9-22.03.5`. We executed the following commands:

./scripts/feeds update -a
make defconfig
./scripts/feeds install libnl
make V=sc package/libnl/compile

The build gets stuck for several minutes with the following message:

make[1]: Entering directory '/builder'
make[2]: Entering directory '/builder/package/toolchain'
Makefile:735: WARNING: skipping libgomp -- package has no install section
mkdir -p /builder/bin/targets/x86/64/packages /builder/build_dir/target-x86_64_musl/toolchain/ipkg-x86_64/libgcc/CONTROL /builder/staging_dir/target-x86_64_musl/pkginfo
install -d -m0755 /builder/build_dir/target-x86_64_musl/toolchain/ipkg-x86_64/libgcc/lib
cp -fpR /builder/staging_dir/toolchain-x86_64_gcc-12.3.0_musl/lib/libgcc_s.so.* /builder/build_dir/target-x86_64_musl/toolchain/ipkg-x86_64/libgcc/lib/
find /builder/build_dir/target-x86_64_musl/toolchain/ipkg-x86_64/libgcc -name 'CVS' -o -name '.svn' -o -name '.#*' -o -name '*~'| xargs -r rm -rf
export CROSS="x86_64-openwrt-linux-musl-"  NO_RENAME=1 ; NM="x86_64-openwrt-linux-musl-nm" STRIP="/builder/staging_dir/host/bin/sstrip -z" STRIP_KMOD="/builder/scripts/strip-kmod.sh" PATCHELF="/builder/staging_dir/host/bin/patchelf" /builder/scripts/rstrip.sh /builder/build_dir/target-x86_64_musl/toolchain/ipkg-x86_64/libgcc
rstrip.sh: /builder/build_dir/target-x86_64_musl/toolchain/ipkg-x86_64/libgcc/lib/libgcc_s.so.1: shared object
(cd /builder/build_dir/target-x86_64_musl/toolchain/ipkg-x86_64/libgcc/CONTROL; ( echo "$CONTROL"; printf "Description: "; echo "$DESCRIPTION" | sed -e 's,^[[:space:]]*, ,g'; ) > control; chmod 644 control; ( echo "#!/bin/sh"; echo "[ \"\${IPKG_NO_SCRIPT}\" = \"1\" ] && exit 0"; echo "[ -s "\${IPKG_INSTROOT}/lib/functions.sh" ] || exit 0"; echo ". \${IPKG_INSTROOT}/lib/functions.sh"; echo "default_postinst \$0 \$@";
) > postinst; ( echo "#!/bin/sh"; echo "[ -s "\${IPKG_INSTROOT}/lib/functions.sh" ] || exit 0"; echo ". \${IPKG_INSTROOT}/lib/functions.sh"; echo "default_prerm \$0 \$@"; ) > prerm; chmod 0755 postinst prerm;
)
install -d -m0755 /builder/bin/targets/x86/64/packages
/builder/staging_dir/host/bin/fakeroot /builder/staging_dir/host/bin/bash /builder/scripts/ipkg-build -m
"" /builder/build_dir/target-x86_64_musl/toolchain/ipkg-x86_64/libgcc /builder/bin/targets/x86/64/packages

Does anyone know what we are doing wrong, or why it tries to compile the toolchain at all? I thought the sdk contains a precompiled toolchain.

Proper documentation request

I'm trying to use the SDK image to build kmod for my target and I'm totally lost - I can't understand whether it's an image or documentation issue.
I'm trying to build for Xiaomi AX9000 it has ipq807x target with generic subtarget. What I tried to do:

  1. Pulled an image openwrt/sdk:ipq807x-generic-v23.05.0 and ran it as usual.
  2. Updated the feeds ./scripts/feeds update -a and after exploring a bit discovered that this v23.05.0 image builds 23.05 branch instead of tag that has commit hash 6637af95aa (at least the official build for my device) Is it okay?
  3. Tried to create .config and that's where all the problems started. Running make menuconfig starts the configuration interface, however it's impossible to change target in it. If I save it "as is" and open the resulting .config, I can see that it has a weird default target CONFIG_TARGET_BOARD=bcm27xx (is it RPi 3?) This target is aarch64-cortexa53 too but it's not ipq807x obviously. Leaving the target as is produces the kmod that I obviously can't install.

Am I doing something wrong? Is it an image issue? Or maybe SDK problem? I'm new to OpenWrt build system and I definitely don't want to assemble build environment on the host.

Provide OpenWrt images

I would like to be able to spin up instances for testing purposes.

Example Dockerfile

FROM openwrtorg/openwrt:18.06.4

RUN opkg update && opkg install luci

mikrotik container

hi
how to deploy openwrt in
I import this image in mikrotik container but mikrotik running then immediately stop
plz help me

Docker exits in host network mode

Hello!

I want to use OpenWRT on an embedded device running docker. I have observed the following behaviour both on my development laptop and on the target device:

$ time docker run --network host openwrtorg/rootfs:x86-64-19.07.2
/etc/preinit: line 6: can't create /sys/devices/system/cpu/microcode/reload: Read-only file system
Press the [f] key and hit [enter] to enter failsafe mode
Press the [1], [2], [3] or [4] key and hit [enter] to select the debug level

real	0m3,011s
user	0m0,045s
sys	0m0,028s

I am using time to give additional data, the same thing happens if I run without it. Also, I believe I need to use the --cap-add NET_ADMIN parameter to allow OpenWRT to make changes, but it does not seem to make a difference for now.

If I start the container using docker run --network host -it openwrtorg/rootfs:x86-64-19.07.2 ash I get a shell and I'm able to do some things, but important services like ubus are not running.

Is this a problem with init? /etc/init.d/rcS doesn't exist even though it's referenced by /etc/inittab. Any help locating the source of the problem would be appreciated!

Dockerๅฎ‰่ฃ…ๅœจopenWrtไธญ๏ผˆๆ— ่ฎบๆ˜ฏๅฆๅผ€ๅฏ๏ผ‰ไผšๅฏผ่‡ดxray็š„Fullconeๆ— ๆ•ˆใ€‚

้—ฎ้ข˜ๆ่ฟฐ

Dockerๅฎ‰่ฃ…ๅœจopenWrtไธญ๏ผˆๆ— ่ฎบๆ˜ฏๅฆๅผ€ๅฏ๏ผ‰ไผšๅฏผ่‡ดxray็š„Fullconeๆ— ๆ•ˆใ€‚


็›ธๅŒๆกˆไพ‹ไผ ้€้—จ๏ผš
xiaorouji/openwrt-passwall#1438
xiaorouji/openwrt-passwall#1320

Invalid reference format

When using the script: docker-sdk.sh
with:

  • VERSION 18.06.1
  • TARGETS=x86-64

I run into the following error:

+ docker build --build-arg CI_REGISTRY_IMAGE --file ./build/Dockerfile --tag ojhgdohtnzzzgjaignmpkosogddrugtp ./build
Sending build context to Docker daemon    350MB
Step 1/8 : ARG CI_REGISTRY_IMAGE
Step 2/8 : FROM $CI_REGISTRY_IMAGE:base
invalid reference format
+ exit 1

threw by docker-build.sh at line 9:

docker build \
	--build-arg CI_REGISTRY_IMAGE \
	--file "./build/Dockerfile" \
	--tag "$TMP_IMAGE_NAME" \
	./build

A new kernel breaks image builder images

I understand that 22.03 (SNAPHOT) images are built once week, but they periodically break for up to seven days when a kernel is refreshed: below is an attempt to generate a 22.03-SNAPSHOT image right now. The issue will resolve itself in five days or so when a new image builder image is generated.

Is it possible to refresh these images each time a new kernel is built?

Configuring arp-scan.
Configuring collectd-mod-sqm.
Collected errors:
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.194-1-7865481e154fa056bd3b6ca1ae9b5f74) for kmod-crypto-md5
 * satisfy_dependencies_for: Cannot satisfy the following dependencies for iputils-ping:
 * 	kernel (= 5.10.194-1-7865481e154fa056bd3b6ca1ae9b5f74)
 * opkg_install_cmd: Cannot install package iputils-ping.
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.194-1-7865481e154fa056bd3b6ca1ae9b5f74) for kmod-i2c-smbus
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.194-1-7865481e154fa056bd3b6ca1ae9b5f74) for kmod-i2c-i801
 * satisfy_dependencies_for: Cannot satisfy the following dependencies for kmod-i2c-i801:
 * 	kernel (= 5.10.194-1-7865481e154fa056bd3b6ca1ae9b5f74)
 * opkg_install_cmd: Cannot install package kmod-i2c-i801.
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.194-1-7865481e154fa056bd3b6ca1ae9b5f74) for kmod-input-core
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.194-1-7865481e154fa056bd3b6ca1ae9b5f74) for kmod-nls-base
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.194-1-7865481e154fa056bd3b6ca1ae9b5f74) for kmod-usb-core
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.194-1-7865481e154fa056bd3b6ca1ae9b5f74) for kmod-usb-hid
 * satisfy_dependencies_for: Cannot satisfy the following dependencies for kmod-usb-hid:
 * 	kernel (= 5.10.194-1-7865481e154fa056bd3b6ca1ae9b5f74)
 * opkg_install_cmd: Cannot install package kmod-usb-hid.
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.194-1-7865481e154fa056bd3b6ca1ae9b5f74) for kmod-libphy
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.194-1-7865481e154fa056bd3b6ca1ae9b5f74) for kmod-usb-net
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.194-1-7865481e154fa056bd3b6ca1ae9b5f74) for kmod-usb-net-asix-ax88179
 * satisfy_dependencies_for: Cannot satisfy the following dependencies for kmod-usb-net-asix-ax88179:
 * 	kernel (= 5.10.194-1-7865481e154fa056bd3b6ca1ae9b5f74)
 * opkg_install_cmd: Cannot install package kmod-usb-net-asix-ax88179.
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.194-1-7865481e154fa056bd3b6ca1ae9b5f74) for kmod-usb-net-cdc-ether
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.194-1-7865481e154fa056bd3b6ca1ae9b5f74) for kmod-usb-net-rtl8152
 * satisfy_dependencies_for: Cannot satisfy the following dependencies for kmod-usb-net-rtl8152:
 * 	kernel (= 5.10.194-1-7865481e154fa056bd3b6ca1ae9b5f74)
 * opkg_install_cmd: Cannot install package kmod-usb-net-rtl8152.
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.194-1-7865481e154fa056bd3b6ca1ae9b5f74) for kmod-ikconfig
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.194-1-7865481e154fa056bd3b6ca1ae9b5f74) for kmod-veth
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.194-1-7865481e154fa056bd3b6ca1ae9b5f74) for kmod-sched-cake
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.194-1-7865481e154fa056bd3b6ca1ae9b5f74) for kmod-ifb
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.194-1-7865481e154fa056bd3b6ca1ae9b5f74) for kmod-nf-reject
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.194-1-7865481e154fa056bd3b6ca1ae9b5f74) for kmod-nf-ipt
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.194-1-7865481e154fa056bd3b6ca1ae9b5f74) for kmod-nf-log
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.194-1-7865481e154fa056bd3b6ca1ae9b5f74) for kmod-ipt-core
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.194-1-7865481e154fa056bd3b6ca1ae9b5f74) for kmod-nf-reject6
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.194-1-7865481e154fa056bd3b6ca1ae9b5f74) for kmod-nf-log6
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.194-1-7865481e154fa056bd3b6ca1ae9b5f74) for kmod-lib-crc32c
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.194-1-7865481e154fa056bd3b6ca1ae9b5f74) for kmod-nft-core
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.194-1-7865481e154fa056bd3b6ca1ae9b5f74) for kmod-ipt-ipopt
 * satisfy_dependencies_for: Cannot satisfy the following dependencies for luci-app-sqm:
 * 	kernel (= 5.10.194-1-7865481e154fa056bd3b6ca1ae9b5f74)
 * opkg_install_cmd: Cannot install package luci-app-sqm.
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.194-1-7865481e154fa056bd3b6ca1ae9b5f74) for kmod-nft-offload
 * satisfy_dependencies_for: Cannot satisfy the following dependencies for luci-ssl:
 * 	kernel (= 5.10.194-1-7865481e154fa056bd3b6ca1ae9b5f74)
 * opkg_install_cmd: Cannot install package luci-ssl.
 * satisfy_dependencies_for: Cannot satisfy the following dependencies for luci-app-nlbwmon:
 * 	kernel (= 5.10.194-1-7865481e154fa056bd3b6ca1ae9b5f74)
 * opkg_install_cmd: Cannot install package luci-app-nlbwmon.
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.194-1-7865481e154fa056bd3b6ca1ae9b5f74) for kmod-fs-exfat
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.194-1-7865481e154fa056bd3b6ca1ae9b5f74) for kmod-lib-crc16
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.194-1-7865481e154fa056bd3b6ca1ae9b5f74) for kmod-fs-ext4
 * satisfy_dependencies_for: Cannot satisfy the following dependencies for kmod-fs-ext4:
 * 	kernel (= 5.10.194-1-7865481e154fa056bd3b6ca1ae9b5f74)
 * opkg_install_cmd: Cannot install package kmod-fs-ext4.
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.194-1-7865481e154fa056bd3b6ca1ae9b5f74) for kmod-nls-cp437
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.194-1-7865481e154fa056bd3b6ca1ae9b5f74) for kmod-nls-iso8859-1
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.194-1-7865481e154fa056bd3b6ca1ae9b5f74) for kmod-nls-utf8
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.194-1-7865481e154fa056bd3b6ca1ae9b5f74) for kmod-fs-vfat
 * satisfy_dependencies_for: Cannot satisfy the following dependencies for kmod-fs-vfat:
 * 	kernel (= 5.10.194-1-7865481e154fa056bd3b6ca1ae9b5f74)
 * opkg_install_cmd: Cannot install package kmod-fs-vfat.
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.194-1-7865481e154fa056bd3b6ca1ae9b5f74) for kmod-usb-storage
 * satisfy_dependencies_for: Cannot satisfy the following dependencies for kmod-usb-storage:
 * 	kernel (= 5.10.194-1-7865481e154fa056bd3b6ca1ae9b5f74)
 * opkg_install_cmd: Cannot install package kmod-usb-storage.
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.194-1-7865481e154fa056bd3b6ca1ae9b5f74) for kmod-amazon-ena
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.194-1-7865481e154fa056bd3b6ca1ae9b5f74) for kmod-ptp
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.194-1-7865481e154fa056bd3b6ca1ae9b5f74) for kmod-mdio-devres
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.194-1-7865481e154fa056bd3b6ca1ae9b5f74) for kmod-amd-xgbe
 * satisfy_dependencies_for: Cannot satisfy the following dependencies for kmod-amd-xgbe:
 * 	kernel (= 5.10.194-1-7865481e154fa056bd3b6ca1ae9b5f74)
 * opkg_install_cmd: Cannot install package kmod-amd-xgbe.
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.194-1-7865481e154fa056bd3b6ca1ae9b5f74) for kmod-bnx2
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.194-1-7865481e154fa056bd3b6ca1ae9b5f74) for kmod-button-hotplug
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.194-1-7865481e154fa056bd3b6ca1ae9b5f74) for kmod-e1000
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.194-1-7865481e154fa056bd3b6ca1ae9b5f74) for kmod-e1000e
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.194-1-7865481e154fa056bd3b6ca1ae9b5f74) for kmod-forcedeth
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.194-1-7865481e154fa056bd3b6ca1ae9b5f74) for kmod-hwmon-core
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.194-1-7865481e154fa056bd3b6ca1ae9b5f74) for kmod-igb
 * satisfy_dependencies_for: Cannot satisfy the following dependencies for kmod-igb:
 * 	kernel (= 5.10.194-1-7865481e154fa056bd3b6ca1ae9b5f74)
 * opkg_install_cmd: Cannot install package kmod-igb.
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.194-1-7865481e154fa056bd3b6ca1ae9b5f74) for kmod-igc
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.194-1-7865481e154fa056bd3b6ca1ae9b5f74) for kmod-mdio
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.194-1-7865481e154fa056bd3b6ca1ae9b5f74) for kmod-ixgbe
 * satisfy_dependencies_for: Cannot satisfy the following dependencies for kmod-ixgbe:
 * 	kernel (= 5.10.194-1-7865481e154fa056bd3b6ca1ae9b5f74)
 * opkg_install_cmd: Cannot install package kmod-ixgbe.
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.194-1-7865481e154fa056bd3b6ca1ae9b5f74) for kmod-r8169
 * satisfy_dependencies_for: Cannot satisfy the following dependencies for kmod-r8169:
 * 	kernel (= 5.10.194-1-7865481e154fa056bd3b6ca1ae9b5f74)
 * opkg_install_cmd: Cannot install package kmod-r8169.
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.194-1-7865481e154fa056bd3b6ca1ae9b5f74) for kmod-tg3
 * pkg_hash_check_unresolved: cannot find dependency kernel (= 5.10.194-1-7865481e154fa056bd3b6ca1ae9b5f74) for kmod-lib-crc-ccitt
 * satisfy_dependencies_for: Cannot satisfy the following dependencies for ppp:
 * 	kernel (= 5.10.194-1-7865481e154fa056bd3b6ca1ae9b5f74)
 * opkg_install_cmd: Cannot install package ppp.
 * satisfy_dependencies_for: Cannot satisfy the following dependencies for ppp-mod-pppoe:
 * 	kernel (= 5.10.194-1-7865481e154fa056bd3b6ca1ae9b5f74)
 * opkg_install_cmd: Cannot install package ppp-mod-pppoe.
make[2]: *** [Makefile:172: package_install] Error 255
make[1]: *** [Makefile:127: _call_image] Error 2
make: *** [Makefile:245: image] Error 2

Add 23.05 to cron?

23.05 images on docker hub are outdated, any special reason for not enabling cron for them?

rootfs persistence

what directories need to be made a (docker) volume, in order to make the configuration persistent?

Exiting from top causes container to shut down

For the previous issue I used top inside the container to determine that something was up with urngd. However, consistently when leaving top with a ctrl + c it causes the container itself to crash.

To replicate:

  1. docker run --rm -it openwrtorg/rootfs
  2. top
  3. ctrl + c
  4. wait 2 seconds

mkdir: cannot create directory '/home/build/openwrt/bin/targets': Permission denied

whoami
root

mkdir -p public

docker run --rm -v "$(pwd)"/public/:/home/build/openwrt/bin openwrtorg/imagebuilder make image PACKAGES="wifidog"
Unable to find image 'openwrtorg/imagebuilder:latest' locally
latest: Pulling from openwrtorg/imagebuilder
dc65f448a2e2: Pulling fs layer
974fa924b194: Pulling fs layer
7ca3655cacfd: Pulling fs layer
46820d6b3cc1: Pulling fs layer
37f28a662628: Pulling fs layer
395f379379c5: Pulling fs layer
46820d6b3cc1: Waiting
37f28a662628: Waiting
395f379379c5: Waiting
7ca3655cacfd: Verifying Checksum
7ca3655cacfd: Download complete
dc65f448a2e2: Verifying Checksum
dc65f448a2e2: Download complete
46820d6b3cc1: Verifying Checksum
46820d6b3cc1: Download complete
395f379379c5: Verifying Checksum
395f379379c5: Download complete
37f28a662628: Verifying Checksum
37f28a662628: Download complete
974fa924b194: Verifying Checksum
974fa924b194: Download complete
dc65f448a2e2: Pull complete
974fa924b194: Pull complete
7ca3655cacfd: Pull complete
46820d6b3cc1: Pull complete
37f28a662628: Pull complete
395f379379c5: Pull complete
Digest: sha256:355c90f9d3c58a4452cf15daa577303f0ca62c4c67fa40c0cebdb1d667da3e11
Status: Downloaded newer image for openwrtorg/imagebuilder:latest
Checking 'working-make'... ok.
Checking 'case-sensitive-fs'... ok.
Checking 'proper-umask'... ok.
Checking 'gcc'... ok.
Checking 'working-gcc'... ok.
Checking 'g++'... ok.
Checking 'working-g++'... ok.
Checking 'ncurses'... ok.
Checking 'perl-thread-queue'... ok.
Checking 'tar'... ok.
Checking 'find'... ok.
Checking 'bash'... ok.
Checking 'patch'... ok.
Checking 'diff'... ok.
Checking 'cp'... ok.
Checking 'seq'... ok.
Checking 'awk'... ok.
Checking 'grep'... ok.
Checking 'getopt'... ok.
Checking 'stat'... ok.
Checking 'unzip'... ok.
Checking 'bzip2'... ok.
Checking 'wget'... ok.
Checking 'perl'... ok.
Checking 'python2-cleanup'... ok.
Checking 'python'... ok.
Checking 'python3'... ok.
Checking 'git'... ok.
Checking 'file'... ok.
Checking 'ldconfig-stub'... ok.
Building images for x86 - Generic x86/64
Packages: wifidog base-files busybox dnsmasq dropbear e2fsprogs firewall fstools ip6tables iptables kernel kmod-bnx2 kmod-button-hotplug kmod-e1000 kmod-e1000e kmod-igb kmod-ipt-offload kmod-r8169 libc libgcc logd mkf2fs mtd netifd odhcp6c odhcpd-ipv6only opkg partx-utils ppp ppp-mod-pppoe uci uclient-fetch urandom-seed urngd
mkdir: cannot create directory '/home/build/openwrt/bin/targets': Permission denied
make[1]: *** [Makefile:116: _call_image] Error 1
make: *** [Makefile:197: image] Error 2

Dockerfile: add "feeds.conf" to "imagebuilder" too

Hi,

The official docker image could be used with the feed scripts (./scripts/feeds) to compile custom packages. However, is quite annoying that the small text file feeds.conf is missing. And this generates a lot of troubles if you don't know why the docker image fails to execute the feed scripts.

So, I suggest to add the default file described in the documentation (https://openwrt.org/docs/guide-developer/feeds):

src-git packages https://git.openwrt.org/feed/packages.git
src-git luci https://git.openwrt.org/project/luci.git
src-git routing https://git.openwrt.org/feed/routing.git
src-git telephony https://git.openwrt.org/feed/telephony.git
#src-git video https://github.com/openwrt/video.git
#src-git targets https://github.com/openwrt/targets.git
#src-git management https://github.com/openwrt-management/packages.git
#src-git oldpackages http://git.openwrt.org/packages.git
#src-link custom /usr/src/openwrt/custom-feed

I hope you agree with that.
Regards.

Cross architecture rootfs images are declared as amd64

> docker pull openwrtorg/rootfs:mips_24kc
mips_24kc: Pulling from openwrtorg/rootfs
Digest: sha256:44e17879beb8da4b64aad5569fbe550ec7320f0f390202758db5026b492493cb
Status: Image is up to date for openwrtorg/rootfs:mips_24kc
docker.io/openwrtorg/rootfs:mips_24kc

> docker image inspect openwrtorg/rootfs:mips_24kc | jq '.[].Architecture'
"amd64"

This used to not matter because Docker could be made to run it by setting the architecture explicitly using --platform but now that's not allowed.

> docker run -it --rm --platform=linux/mips_24kc openwrtorg/rootfs:mips_24kc
Unable to find image 'openwrtorg/rootfs:mips_24kc' locally
mips_24kc: Pulling from openwrtorg/rootfs
Digest: sha256:44e17879beb8da4b64aad5569fbe550ec7320f0f390202758db5026b492493cb
Status: Image is up to date for openwrtorg/rootfs:mips_24kc
docker: Error response from daemon: image with reference openwrtorg/rootfs:mips_24kc was found but does not match the specified platform: wanted linux/mips_24kc, actual: linux/amd64.

I suspect you need to set the platforms option here. Edit: I mean here.

Can't check gpg signature when building rootfs

I tried building a rootfs for the latest 19.07 release with:

$ BRANCH=19.07.3 ./docker-rootfs.sh

However it failed to check the gpg signature:

+ export GNUPGHOME=/keys/gpg/
+ GNUPGHOME=/keys/gpg/
+ export USIGNHOME=/keys/usign/
+ USIGNHOME=/keys/usign/
+ curl https://downloads.openwrt.org/releases/19.07.3/targets/x86/64/sha256sums -fs -o sha256sums
+ curl https://downloads.openwrt.org/releases/19.07.3/targets/x86/64/sha256sums.asc -fs -o sha256sums.asc
+ curl https://downloads.openwrt.org/releases/19.07.3/targets/x86/64/sha256sums.sig -fs -o sha256sums.sig
+ '[' '!' -f sha256sums.asc ']'
+ '[' '!' -f sha256sums.asc ']'
+ gpg --with-fingerprint --verify sha256sums.asc sha256sums
gpg: keyblock resource `/keys/gpg//pubring.gpg': file open error
gpg: Signature made Sun 17 May 2020 02:42:57 AM CEST using RSA key ID 2074BE7A
gpg: Can't check signature: public key not found
+ exit 1

Are those /keys/ paths supposed to be on the host system? Obviously it doesn't work in my case because I don't run the script as root...

kmodloader: no module folders for kernel version 6.2.2-arch1-1 found

I have two openwrt containers with the same version. After upgraded and reboot arch linux through pacman -Syu, this errors occurs in dmesg in both two containers.

On container works seems fine,but the other container contstantly get a connection refused error in luci web page and also traffics go through this container get lost periodically(about 4s).

Any guys have met this before? I can supply more logs if needed.

Environment:

  • host arch linux(kernel 6.2.2-arch1-1)
  • openwrtorg/rootfs:x86-64-22.03.3

unstable: high cpu usage by /sbin/urngd

Hi all, getting a lot of instability. On MacOS Mojave, running Docker version 19.03.8, and docker-machine version 0.16.2

If I just use the Readme command:

docker run --rm -it openwrtorg/rootfs

I get a number of error messages during launch:

rich$ docker run --rm -it openwrtorg/rootfs
Failed to resize receive buffer: Operation not permitted
ip: RTNETLINK answers: Operation not permitted
Press the [f] key and hit [enter] to enter failsafe mode
Press the [1], [2], [3] or [4] key and hit [enter] to select the debug level
ip: can't send flush request: Operation not permitted
ip: SIOCSIFFLAGS: Operation not permitted
Please press Enter to activate this console.

When in the shell, it's sluggish, and I notice that one core of my CPU is being used at 100%. A top inside the container reveals the following:

Mem: 433964K used, 579256K free, 290552K shrd, 9536K buff, 323160K cached
CPU:  99% usr   0% sys   0% nic   0% idle   0% io   0% irq   0% sirq
Load average: 0.99 0.58 0.24 2/163 817
  PID  PPID USER     STAT   VSZ %VSZ %CPU COMMAND
   92     1 root     R      780   0% 100% /sbin/urngd
  279     1 root     S     1300   0%   0% /sbin/rpcd -s /var/run/ubus.sock -t 30
  434     1 root     S     1196   0%   0% /sbin/netifd
    1     0 root     S     1116   0%   0% /sbin/procd
   76     1 root     S     1084   0%   0% /bin/ash --login

Am I doing something wrong?

SDKs based on architecutre not target

Currently we build SDKs based on targets while SDKs actually create packages in a specific architecture. We could define those architectures and then add additional tags for compatible architectures. This way we end up producing less containers and make it easier for users to use the SDK in their CIs as they build only once per architecture.

openwrt/imagebuilder:x86-64-v22.03.4 is building master....

@aparcar

REPOSITORY             TAG               IMAGE ID       CREATED        SIZE
openwrt/imagebuilder   x86-64-v22.03.4   09e27754d696   21 hours ago   1.06GB

============================================
cat repositories.conf 
## Place your custom repositories here, they must match the architecture and version.
# src/gz %n https://downloads.openwrt.org/snapshots
# src custom file:///usr/src/openwrt/bin/x86/packages

## Remote package repositories
src/gz openwrt_core https://downloads.openwrt.org/snapshots/targets/x86/64/packages
src/gz openwrt_base https://downloads.openwrt.org/snapshots/packages/x86_64/base
src/gz openwrt_kmods https://downloads.openwrt.org/snapshots/targets/x86/64/kmods/5.15.107-1-e469f5589b4c7b368924a6e4f8f7407f
src/gz openwrt_luci https://downloads.openwrt.org/snapshots/packages/x86_64/luci
src/gz openwrt_packages https://downloads.openwrt.org/snapshots/packages/x86_64/packages
src/gz openwrt_routing https://downloads.openwrt.org/snapshots/packages/x86_64/routing
src/gz openwrt_telephony https://downloads.openwrt.org/snapshots/packages/x86_64/telephony

## This is the local package repository, do not remove!
src imagebuilder file:packages

option check_signature

=========================================================
Building package index...
Downloading https://downloads.openwrt.org/snapshots/targets/x86/64/packages/Packages.gz
Updated list of available packages in /builder/build_dir/target-x86_64_musl/root-x86/../../../../builder/dl/openwrt_core
Downloading https://downloads.openwrt.org/snapshots/targets/x86/64/packages/Packages.sig
Signature check passed.
Downloading https://downloads.openwrt.org/snapshots/packages/x86_64/base/Packages.gz
Updated list of available packages in /builder/build_dir/target-x86_64_musl/root-x86/../../../../builder/dl/openwrt_base
Downloading https://downloads.openwrt.org/snapshots/packages/x86_64/base/Packages.sig
Signature check passed.
Downloading https://downloads.openwrt.org/snapshots/targets/x86/64/kmods/5.15.107-1-e469f5589b4c7b368924a6e4f8f7407f/Packages.gz
Updated list of available packages in /builder/build_dir/target-x86_64_musl/root-x86/../../../../builder/dl/openwrt_kmods
Downloading https://downloads.openwrt.org/snapshots/targets/x86/64/kmods/5.15.107-1-e469f5589b4c7b368924a6e4f8f7407f/Packages.sig
Signature check passed.
Downloading https://downloads.openwrt.org/snapshots/packages/x86_64/luci/Packages.gz
Updated list of available packages in /builder/build_dir/target-x86_64_musl/root-x86/../../../../builder/dl/openwrt_luci
Downloading https://downloads.openwrt.org/snapshots/packages/x86_64/luci/Packages.sig
Signature check passed.
Downloading https://downloads.openwrt.org/snapshots/packages/x86_64/packages/Packages.gz
Updated list of available packages in /builder/build_dir/target-x86_64_musl/root-x86/../../../../builder/dl/openwrt_packages
Downloading https://downloads.openwrt.org/snapshots/packages/x86_64/packages/Packages.sig
Signature check passed.
Downloading https://downloads.openwrt.org/snapshots/packages/x86_64/routing/Packages.gz
Updated list of available packages in /builder/build_dir/target-x86_64_musl/root-x86/../../../../builder/dl/openwrt_routing
Downloading https://downloads.openwrt.org/snapshots/packages/x86_64/routing/Packages.sig
Signature check passed.
Downloading https://downloads.openwrt.org/snapshots/packages/x86_64/telephony/Packages.gz
Updated list of available packages in /builder/build_dir/target-x86_64_musl/root-x86/../../../../builder/dl/openwrt_telephony
Downloading https://downloads.openwrt.org/snapshots/packages/x86_64/telephony/Packages.sig
Signature check passed.
Downloading file:packages/Packages
Updated list of available packages in /builder/build_dir/target-x86_64_musl/root-x86/../../../../builder/dl/imagebuilder
Downloading file:packages/Packages.sig
Signature check passed.

Installing packages...
Installing libc (1.2.3-4) to root...
Installing libgcc1 (12.2.0-4) to root...
Downloading https://downloads.openwrt.org/snapshots/targets/x86/64/packages/libgcc1_12.2.0-4_x86_64.ipk
Configuring libgcc1.
Configuring libc.
Installing kernel (5.15.107-1-e469f5589b4c7b368924a6e4f8f7407f) to root...
Configuring kernel.
Installing htop (3.2.2-1) to root...
Downloading https://downloads.openwrt.org/snapshots/packages/x86_64/packages/htop_3.2.2-1_x86_64.ipk
Installing terminfo (6.4-2) to root...
Downloading https://downloads.openwrt.org/snapshots/packages/x86_64/base/terminfo_6.4-2_x86_64.ipk
Installing libncurses6 (6.4-2) to root...
Downloading https://downloads.openwrt.org/snapshots/packages/x86_64/base/libncurses6_6.4-2_x86_64.ipk

Docker cant run image openwrtorg/rootfs:x86-64

Hello, I encountered the following problems when using Docker. Can you help me?

Error by docker build

Collected errors:
 * satisfy_dependencies_for: Cannot satisfy the following dependencies for luci-mod-admin-full:
 * 	kernel (= 5.4.38-1-9dea1f6ed59a3231b5bc094092a9414a)
 * opkg_install_cmd: Cannot install package luci-mod-admin-full.

Dockerfile

FROM openwrtorg/rootfs:x86-64

MAINTAINER Zhao ZHANG <[email protected]>

USER root

RUN mkdir /var/lock && \
    opkg update && \
    opkg install uhttpd luci-base luci-mod-admin-full luci-theme-bootstrap luci-i18n-base-en luci-i18n-firewall-en luci-i18n-base-fr luci-i18n-firewall-fr && \
    uci set luci.ccache.enable=0 && \
    uci commit luci

EXPOSE 80

Consider using OCI Image manifest fields like platform/arch/os instead of platform/arch tags

Current the use of tags for different architecture might not be the recommended way to distribute containers for different platforms/architecture/os. See https://docs.docker.com/engine/reference/commandline/manifest/#manifest-annotate

https://docs.docker.com/registry/spec/manifest-v2-2/
https://github.com/opencontainers/image-spec/blob/main/image-index.md

If enabled the container specification in docker-compose/kubernetes config won't have to worry about specifying the right architecture tag.

Run external binary

Hello all,

I pulled openwrtorg/rootfs and ran it like this
docker run --rm -it -v /home/mjshin/MyCode:/tmp openwrtorg/rootfs

In /tmp, I tried to run my own linux based application but it could not work well.
root@ca16d6d79408:/tmp# ls -al hello
-rwxrwxr-x 1 1000 1000 16688 Sep 20 03:16 hello
root@ca16d6d79408:/tmp# ./hello
/bin/ash: ./hello: not found
root@ca16d6d79408:/tmp#

What was wrong in my case ?

Thanks,
Myungjoon

no network with net_admin Capability

I am trying to use this docker image to run n2n vpn, the vpn needs tuntap, so the net_admin with /dev/net/tun device is needed, however openwrt docker witih net_admin can not connect to internet, the eth0 cannot get ip address, fails with static address either.
it seems /sbin/init cannot correctly config network, can anyone tell me how to config the docker image?

version: '3.1'

services:

openwrt:
image: openwrtorg/rootfs:openwrt-21.02
restart: always
container_name: openwrt
cap_add:
- NET_ADMIN
devices:
- /dev/net/tun
ports:
- 8082:80

Unable to find user root: no matching entries in passwd file

docker run --rm -it openwrtorg/rootfs:x86-64
Unable to find image 'openwrtorg/rootfs:x86-64' locally
x86-64: Pulling from openwrtorg/rootfs
90126f32b86a: Pull complete
Digest: sha256:d48323467d4813be476105dd80cc58fd9d7ca613de80ecfcc758aa4f414269c3
Status: Downloaded newer image for openwrtorg/rootfs:x86-64
docker: Error response from daemon: linux spec user: unable to find user root: no matching entries in passwd file.

Per the example at: https://hub.docker.com/r/openwrtorg/rootfs

Missing 5.4.75-1-635c1c3a44da708172b381dc7312ac40 Folder

Hi,

I pulled openwrtorg/rootfs:x86-64, and run a container base on it. But when I was executing the opkg update command, I got the issue below:
`/ # opkg update
Downloading https://downloads.openwrt.org/snapshots/targets/x86/64/packages/Packages.gz
Updated list of available packages in /var/opkg-lists/openwrt_core
Downloading https://downloads.openwrt.org/snapshots/targets/x86/64/packages/Packages.sig
Signature check passed.
Downloading https://downloads.openwrt.org/snapshots/packages/x86_64/base/Packages.gz
Updated list of available packages in /var/opkg-lists/openwrt_base
Downloading https://downloads.openwrt.org/snapshots/packages/x86_64/base/Packages.sig
Signature check passed.
Downloading https://downloads.openwrt.org/snapshots/targets/x86/64/kmods/5.4.75-1-635c1c3a44da708172b381dc7312ac40/Packages.gz
*** Failed to download the package list from https://downloads.openwrt.org/snapshots/targets/x86/64/kmods/5.4.75-1-635c1c3a44da708172b381dc7312ac40/Packages.gz

Downloading https://downloads.openwrt.org/snapshots/packages/x86_64/freifunk/Packages.gz
Updated list of available packages in /var/opkg-lists/openwrt_freifunk
Downloading https://downloads.openwrt.org/snapshots/packages/x86_64/freifunk/Packages.sig
Signature check passed.
Downloading https://downloads.openwrt.org/snapshots/packages/x86_64/luci/Packages.gz
Updated list of available packages in /var/opkg-lists/openwrt_luci
Downloading https://downloads.openwrt.org/snapshots/packages/x86_64/luci/Packages.sig
Signature check passed.
Downloading https://downloads.openwrt.org/snapshots/packages/x86_64/packages/Packages.gz
Updated list of available packages in /var/opkg-lists/openwrt_packages
Downloading https://downloads.openwrt.org/snapshots/packages/x86_64/packages/Packages.sig
Signature check passed.
Downloading https://downloads.openwrt.org/snapshots/packages/x86_64/routing/Packages.gz
Updated list of available packages in /var/opkg-lists/openwrt_routing
Downloading https://downloads.openwrt.org/snapshots/packages/x86_64/routing/Packages.sig
Signature check passed.
Downloading https://downloads.openwrt.org/snapshots/packages/x86_64/telephony/Packages.gz
Updated list of available packages in /var/opkg-lists/openwrt_telephony
Downloading https://downloads.openwrt.org/snapshots/packages/x86_64/telephony/Packages.sig
Signature check passed.
Collected errors:

And checked on "https://downloads.openwrt.org/snapshots/targets/x86/64/kmods/ " no folder named 5.4.75-1-635c1c3a44da708172b381dc7312ac40 was found, how can I fix this issue?

raspberry pi4 8gb with docker . need support for create image or deploy all

i try deploy on my raspberry pi 4 8gb

uname -a
Linux raspberrypi 5.10.92-v8+ #1514 SMP PREEMPT Mon Jan 17 17:39:38 GMT 2022 aarch64 GNU/Linux

with docker

root@raspberrypi:/openwrt# docker -v
Docker version 20.10.12, build e91ed57

but i dont undestand the procedure because i clone git and execute

/docker-build.sh $VERSION=21.02.1 $TARGET=aarch64_generi $DOCKER_USER=admin $DOCKER_PASS=admin

  • cp '' ./build/Dockerfile
    cp: impossibile eseguire stat di '': File o directory non esistente

but nothing

i try with

root@raspberrypi:/openwrt# docker run --rm -it openwrtorg/aarch64_generic
Unable to find image 'openwrtorg/aarch64_generic:latest' locally
docker: Error response from daemon: pull access denied for openwrtorg/aarch64_generic, repository does not exist or may require 'docker login': denied: requested access to the resource is denied.
See 'docker run --help'.

but nothing

can help me

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.