Andrey Smirnov
Andrey Smirnov
I understand this issue, but I'm not sure how we could implement it...
@Commod0re I'm not able to reproduce that (neither in tests nor reproducing your scenario): ``` $ aptly mirror create -architectures=amd64 -filter='Name (~ python)' wheezy http://mirror.yandex.ru/debian wheezy $ aptly mirror update...
That makes sense: first aptly does filtering, then dependency resolution. As dependency resolution algorithm isn't perfect, it may produce different result on slightly different package order.
> I don't think this is a correct change in runc level. Eg. in @smira system where he has `sys_boot` disabled, when a user runs `docker run --cap-add SYS_BOOT` it...
I mean that on other hand how can `docker` (or any other client in general) know what are the capabilities available to `dockerd` ?
thanks @tonistiigi for the clarification, yep, it makes perfect sense
Please do that! more distributions channels is good!
At the moment Talos doesn't support diskless operations. Talos can boot over the network, but it still requires a system disk that it's going to own. Talos creates `/var` partition...
It looks like things fail with our "test" DHCP server, but we can fix that of course. This test DHCP server was never supposed to be complete implementation.