Turris OS packages issueshttps://gitlab.nic.cz/turris/os/packages/-/issues2019-12-10T16:03:58+01:00https://gitlab.nic.cz/turris/os/packages/-/issues/354lxc: unable to run systemd container2019-12-10T16:03:58+01:00Karel Kocilxc: unable to run systemd containerSystemd based containers such as Debian are failing with following error:
```
lxc-start: debian: utils.c: safe_mount: 1707 No such file or directory - Failed to mount /usr/lib/lxc/rootfs/proc/tty onto /usr/lib/lxc/rootfs/proc/sys/net
...Systemd based containers such as Debian are failing with following error:
```
lxc-start: debian: utils.c: safe_mount: 1707 No such file or directory - Failed to mount /usr/lib/lxc/rootfs/proc/tty onto /usr/lib/lxc/rootfs/proc/sys/net
Failed to mount cgroup at /sys/fs/cgroup/systemd: Operation not permitted
```
```
lxc-start: opensuse: utils.c: safe_mount: 1707 No such file or directory - Failed to mount /usr/lib/lxc/rootfs/proc/tty onto /usr/lib/lxc/rootfs/proc/sys/net
Failed to mount cgroup at /sys/fs/cgroup/systemd: Operation not permitted
```
I suspect that we don;t have appropriate kernel configuration.Michal HruseckyMichal Hruseckyhttps://gitlab.nic.cz/turris/os/packages/-/issues/355lxc: network is not configured in default2019-09-27T12:53:19+02:00Karel Kocilxc: network is not configured in defaultWe should provide default LXC network configuration that would be connected to LAN. At the moment there is no default configuration and containers start without network.
As an example Alpine edge:
```root@turris:~# lxc-start -F -n alpin...We should provide default LXC network configuration that would be connected to LAN. At the moment there is no default configuration and containers start without network.
As an example Alpine edge:
```root@turris:~# lxc-start -F -n alpine
lxc-start: alpine: utils.c: safe_mount: 1707 No such file or directory - Failed to mount /usr/lib/lxc/rootfs/proc/tty onto /usr/lib/lxc/rootfs/proc/sys/net
OpenRC 0.41.2.f4b2a85138 is starting up Linux 4.14.111 (aarch64) [LXC]
* /proc is already mounted
* /run/openrc: creating directory
* /run/lock: creating directory
* /run/lock: correcting owner
* Caching service dependencies ... [ ok ]
* Migrating /var/lock to /run/lock ... [ ok ]
* Creating user login records ... [ ok ]
* Wiping /tmp directory ... [ ok ]
* Starting busybox syslog ... [ ok ]
* Starting busybox crond ... [ ok ]
* Starting networking ... * eth0 ...ip: ioctl 0x8913 failed: No such device
[ !! ]
* ERROR: networking failed to start
Welcome to Alpine Linux 3.8
Kernel 4.14.111 on an aarch64 (/dev/console)
alpine login: root
Welcome to Alpine!
The Alpine Wiki contains a large amount of how-to guides and general
information about administrating Alpine systems.
See <http://wiki.alpinelinux.org/>.
You can setup the system with the command: setup-alpine
You may change this message by editing /etc/motd.
alpine:~# ip l
1: lo: <LOOPBACK> mtu 65536 qdisc noop state DOWN qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: ip6tnl0@NONE: <NOARP> mtu 1452 qdisc noop state DOWN qlen 1000
link/tunnel6 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00 brd 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00
3: sit0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN qlen 1000
link/sit 0.0.0.0 brd 0.0.0.0
alpine:~#
```Turris OS 4.0Michal HruseckyMichal Hruseckyhttps://gitlab.nic.cz/turris/os/packages/-/issues/521pyzmq is not being compiled (unrecognized -R)2020-02-20T16:40:04+01:00Josef Schlehoferpyzmq is not being compiled (unrecognized -R)pyzmq fails in HBD branch (Turris OS 5.x - OpenWrt 19.07) and it is required by package `sentinel-dynfw-client`.
Faillog:
```
aarch64-openwrt-linux-musl-gcc: error: unrecognized command line option '-R'
error: command 'ccache_cc' failed...pyzmq fails in HBD branch (Turris OS 5.x - OpenWrt 19.07) and it is required by package `sentinel-dynfw-client`.
Faillog:
```
aarch64-openwrt-linux-musl-gcc: error: unrecognized command line option '-R'
error: command 'ccache_cc' failed with exit status 1
```
My findings:
- https://github.com/rbgirshick/py-faster-rcnn/issues/706
- https://stackoverflow.com/a/56605633
When I followed from the first link the instructions to replace 'R' to '-Wl,-rpath=' in these four files:
```
build_dir/hostpkg/Python-3.7.5/Lib/distutils/unixccompiler.py
staging_dir/hostpkg/lib/python3.7/distutils/unixccompiler.py
staging_dir/target-aarch64_cortex-a53_musl/usr/lib/python3.7/distutils/unixccompiler.py
staging_dir/target-aarch64_cortex-a53_musl/root-mvebu/usr/lib/python3.7/distutils/unixccompiler.py
```
and then run `make package/pyzmq/{clean,compile} -j4 V=s`, I was able to successfully compile pyzmq for Turris MOX.
I'm looking into it more.Turris OS 5.0https://gitlab.nic.cz/turris/os/packages/-/issues/578/etc/resolver/dhcp_host_domain_ng.py broken in TurrisOS 5.0.02023-08-16T14:41:08+02:00Leonardo Brondani Schenkel/etc/resolver/dhcp_host_domain_ng.py broken in TurrisOS 5.0.0Trying out the `hbt` branch on Turris Omnia.
```
/etc/turris-version: 5.0.0
knot-resolver - 5.0.1-1.0
resolver-conf - 0.0.1-38.2
```
When running `/etc/resolver/dhcp_host_domain_ng.py`, nothing happens and the following gets logged:
```
...Trying out the `hbt` branch on Turris Omnia.
```
/etc/turris-version: 5.0.0
knot-resolver - 5.0.1-1.0
resolver-conf - 0.0.1-38.2
```
When running `/etc/resolver/dhcp_host_domain_ng.py`, nothing happens and the following gets logged:
```
turris dhcp_host_domain_ng.py: Kresd is probably not running no socket found.
```
I checked the source and it's due to this snippet:
```python
def _get_socket_path(self):
path = os.path.join(uci_get("resolver.kresd.rundir"), "tty")
try:
files = [f for f in listdir(path)]
return os.path.join(path, files[0])
except:
log("Kresd is probably not running no socket found.", LOG_ERR)
sys.exit(1)
```
But note that `kresd` does not create the `tty` directory any longer, it is named `control`:
```
# tree /tmp/kresd
/tmp/kresd
├── control
│ └── 32112
├── data.mdb
├── hints.tmp
└── lock.mdb
```
Once I manually edit the script to use `control`, then it works:
```
turris dhcp_host_domain_ng.py: Refresh kresd leases
```Turris OS 5.0Jan PavlinecJan Pavlinechttps://gitlab.nic.cz/turris/os/packages/-/issues/794Networking in TOS 6.0 on MOX doesn't work2022-04-14T12:19:06+02:00Lukas JelinekNetworking in TOS 6.0 on MOX doesn't workIn Turris OS 6.0 (HBD) on MOX, networking doesn't work at all after booting. It can be temporarily fixed by assigning an address to a port (the `br-lan` bridge respectively) but this assignment doesn't persist over disconnecting and reco...In Turris OS 6.0 (HBD) on MOX, networking doesn't work at all after booting. It can be temporarily fixed by assigning an address to a port (the `br-lan` bridge respectively) but this assignment doesn't persist over disconnecting and reconnecting the cable.