Jump to content
funtoo forums

walterw

Members
  • Content count

    14
  • Joined

  • Last visited

  1. ANSWERED Unable to start lxd container

    Thanks, that fixed it - I followed the gentoo docs and not the funtoo ones.
  2. I am trying to launch a container with lxd and am not having any such luck. These are the steps I followed: https://wiki.gentoo.org/wiki/LXD 1. install lxd (I did not install criu and will add that for a future build) 2. manually configure kernel for lxd (I didn't do ebuild lxc or ebuild criu) 3. lxd group / user didn't exist, so I created it 4. add myself to that group 5. started lxd 6. initialized lxd (the order on the gentoo website says otherwise, but I couldn't do it in that order) 7. lxd automatically setup the network interface via the lxd service, so I didn't have the net.lxbr0 to worry about 8. images repository already existed, I just chose alpine linux since it was tiny lxc launch images:alpine/3.4 Creating the container Container name is: peaceful-racer Starting peaceful-racer error: Failed to run: /usr/sbin/lxd forkstart peaceful-racer /var/lib/lxd/containers /var/log/lxd/peaceful-racer/lxc.conf: Try `lxc info --show-log local:peaceful-racer` for more info lxc info --show-log local:peaceful-racer Name: peaceful-racer Remote: unix:// Architecture: x86_64 Created: 2018/03/13 10:24 UTC Status: Stopped Type: persistent Profiles: default Log: lxc 20180313102453.772 WARN lxc_monitor - monitor.c:lxc_monitor_fifo_send:111 - Failed to open fifo to send message: No such file or directory. lxc 20180313102453.772 WARN lxc_monitor - monitor.c:lxc_monitor_fifo_send:111 - Failed to open fifo to send message: No such file or directory. lxc 20180313102454.308 ERROR lxc_conf - conf.c:lxc_map_ids:2736 - newuidmap failed to write mapping "": newuidmap 18127 0 1000000 1000000000 lxc 20180313102454.309 ERROR lxc_start - start.c:lxc_spawn:1276 - Failed to set up id mapping. lxc 20180313102454.448 WARN lxc_network - network.c:lxc_delete_network_priv:2557 - Failed to remove interface "vethPDC82W" from "lxdbr0": Invalid argument lxc 20180313102454.448 WARN lxc_monitor - monitor.c:lxc_monitor_fifo_send:111 - Failed to open fifo to send message: No such file or directory. lxc 20180313102454.448 WARN lxc_monitor - monitor.c:lxc_monitor_fifo_send:111 - Failed to open fifo to send message: No such file or directory. lxc 20180313102454.449 ERROR lxc_container - lxccontainer.c:wait_on_daemonized_start:760 - Received container state "ABORTING" instead of "RUNNING" lxc 20180313102454.452 ERROR lxc_start - start.c:__lxc_start:1459 - Failed to spawn container "peaceful-racer". lxc 20180313102454.452 WARN lxc_monitor - monitor.c:lxc_monitor_fifo_send:111 - Failed to open fifo to send message: No such file or directory. lxc 20180313102454.452 WARN lxc_monitor - monitor.c:lxc_monitor_fifo_send:111 - Failed to open fifo to send message: No such file or directory. lxc 20180313102454.610 ERROR lxc_conf - conf.c:lxc_map_ids:2736 - newuidmap failed to write mapping "": newuidmap 18143 0 1000000 1000000000 1000000000 0 1 lxc 20180313102454.611 ERROR lxc_conf - conf.c:userns_exec_1:3824 - error setting up {g,u}id mappings for child process "18143" lxc 20180313102454.611 ERROR lxc_cgfsng - cgroups/cgfsng.c:recursive_destroy:1286 - Error destroying /sys/fs/cgroup/openrc//lxc/peaceful-racer lxc 20180313102454.645 ERROR lxc_conf - conf.c:lxc_map_ids:2736 - newuidmap failed to write mapping "": newuidmap 18145 0 1000000 1000000000 1000000000 0 1 lxc 20180313102454.645 ERROR lxc_conf - conf.c:userns_exec_1:3824 - error setting up {g,u}id mappings for child process "18145" lxc 20180313102454.645 ERROR lxc_cgfsng - cgroups/cgfsng.c:recursive_destroy:1286 - Error destroying /sys/fs/cgroup/cpuset//lxc/peaceful-racer lxc 20180313102454.676 ERROR lxc_conf - conf.c:lxc_map_ids:2736 - newuidmap failed to write mapping "": newuidmap 18147 0 1000000 1000000000 1000000000 0 1 lxc 20180313102454.677 ERROR lxc_conf - conf.c:userns_exec_1:3824 - error setting up {g,u}id mappings for child process "18147" lxc 20180313102454.677 ERROR lxc_cgfsng - cgroups/cgfsng.c:recursive_destroy:1286 - Error destroying /sys/fs/cgroup/cpu//lxc/peaceful-racer lxc 20180313102454.708 ERROR lxc_conf - conf.c:lxc_map_ids:2736 - newuidmap failed to write mapping "": newuidmap 18149 0 1000000 1000000000 1000000000 0 1 lxc 20180313102454.709 ERROR lxc_conf - conf.c:userns_exec_1:3824 - error setting up {g,u}id mappings for child process "18149" lxc 20180313102454.709 ERROR lxc_cgfsng - cgroups/cgfsng.c:recursive_destroy:1286 - Error destroying /sys/fs/cgroup/cpuacct//lxc/peaceful-racer lxc 20180313102454.743 ERROR lxc_conf - conf.c:lxc_map_ids:2736 - newuidmap failed to write mapping "": newuidmap 18151 0 1000000 1000000000 1000000000 0 1 lxc 20180313102454.743 ERROR lxc_conf - conf.c:userns_exec_1:3824 - error setting up {g,u}id mappings for child process "18151" lxc 20180313102454.743 ERROR lxc_cgfsng - cgroups/cgfsng.c:recursive_destroy:1286 - Error destroying /sys/fs/cgroup/blkio//lxc/peaceful-racer lxc 20180313102454.777 ERROR lxc_conf - conf.c:lxc_map_ids:2736 - newuidmap failed to write mapping "": newuidmap 18153 0 1000000 1000000000 1000000000 0 1 lxc 20180313102454.778 ERROR lxc_conf - conf.c:userns_exec_1:3824 - error setting up {g,u}id mappings for child process "18153" lxc 20180313102454.778 ERROR lxc_cgfsng - cgroups/cgfsng.c:recursive_destroy:1286 - Error destroying /sys/fs/cgroup/memory//lxc/peaceful-racer lxc 20180313102454.810 ERROR lxc_conf - conf.c:lxc_map_ids:2736 - newuidmap failed to write mapping "": newuidmap 18155 0 1000000 1000000000 1000000000 0 1 lxc 20180313102454.811 ERROR lxc_conf - conf.c:userns_exec_1:3824 - error setting up {g,u}id mappings for child process "18155" lxc 20180313102454.811 ERROR lxc_cgfsng - cgroups/cgfsng.c:recursive_destroy:1286 - Error destroying /sys/fs/cgroup/devices//lxc/peaceful-racer lxc 20180313102454.841 ERROR lxc_conf - conf.c:lxc_map_ids:2736 - newuidmap failed to write mapping "": newuidmap 18157 0 1000000 1000000000 1000000000 0 1 lxc 20180313102454.842 ERROR lxc_conf - conf.c:userns_exec_1:3824 - error setting up {g,u}id mappings for child process "18157" lxc 20180313102454.842 ERROR lxc_cgfsng - cgroups/cgfsng.c:recursive_destroy:1286 - Error destroying /sys/fs/cgroup/freezer//lxc/peaceful-racer lxc 20180313102454.874 ERROR lxc_conf - conf.c:lxc_map_ids:2736 - newuidmap failed to write mapping "": newuidmap 18159 0 1000000 1000000000 1000000000 0 1 lxc 20180313102454.874 ERROR lxc_conf - conf.c:userns_exec_1:3824 - error setting up {g,u}id mappings for child process "18159" lxc 20180313102454.875 ERROR lxc_cgfsng - cgroups/cgfsng.c:recursive_destroy:1286 - Error destroying /sys/fs/cgroup/net_cls//lxc/peaceful-racer lxc 20180313102454.903 ERROR lxc_conf - conf.c:lxc_map_ids:2736 - newuidmap failed to write mapping "": newuidmap 18161 0 1000000 1000000000 1000000000 0 1 lxc 20180313102454.903 ERROR lxc_conf - conf.c:userns_exec_1:3824 - error setting up {g,u}id mappings for child process "18161" lxc 20180313102454.903 ERROR lxc_cgfsng - cgroups/cgfsng.c:recursive_destroy:1286 - Error destroying /sys/fs/cgroup/perf_event//lxc/peaceful-racer lxc 20180313102454.928 ERROR lxc_conf - conf.c:lxc_map_ids:2736 - newuidmap failed to write mapping "": newuidmap 18163 0 1000000 1000000000 1000000000 0 1 lxc 20180313102454.929 ERROR lxc_conf - conf.c:userns_exec_1:3824 - error setting up {g,u}id mappings for child process "18163" lxc 20180313102454.929 ERROR lxc_cgfsng - cgroups/cgfsng.c:recursive_destroy:1286 - Error destroying /sys/fs/cgroup/hugetlb//lxc/peaceful-racer lxc 20180313102454.960 ERROR lxc_conf - conf.c:lxc_map_ids:2736 - newuidmap failed to write mapping "": newuidmap 18165 0 1000000 1000000000 1000000000 0 1 lxc 20180313102454.960 ERROR lxc_conf - conf.c:userns_exec_1:3824 - error setting up {g,u}id mappings for child process "18165" lxc 20180313102454.960 ERROR lxc_cgfsng - cgroups/cgfsng.c:recursive_destroy:1286 - Error destroying /sys/fs/cgroup/pids//lxc/peaceful-racer lxc 20180313102454.961 WARN lxc_monitor - monitor.c:lxc_monitor_fifo_send:111 - Failed to open fifo to send message: No such file or directory. lxc 20180313102454.961 WARN lxc_monitor - monitor.c:lxc_monitor_fifo_send:111 - Failed to open fifo to send message: No such file or directory. lxc 20180313102454.963 WARN lxc_commands - commands.c:lxc_cmd_rsp_recv:125 - Command get_cgroup failed to receive response: Connection reset by peer. lxc config --expanded show peaceful-racer architecture: x86_64 config: image.architecture: amd64 image.description: Alpine 3.4 amd64 (20180312_17:50) image.os: Alpine image.release: "3.4" image.serial: "20180312_17:50" volatile.base_image: 2ef5588b926349408eb1689bda8aa2f42123248f1bb3fc34c2ad4d6c5bb02962 volatile.eth0.hwaddr: 00:16:3e:67:65:8b volatile.eth0.name: eth0 volatile.idmap.base: "0" volatile.idmap.next: '[{"Isuid":true,"Isgid":true,"Hostid":1000000,"Nsid":0,"Maprange":1000000000}]' volatile.last_state.idmap: '[{"Isuid":true,"Isgid":true,"Hostid":1000000,"Nsid":0,"Maprange":1000000000}]' volatile.last_state.power: STOPPED devices: eth0: nictype: bridged parent: lxdbr0 type: nic root: path: / pool: default type: disk ephemeral: false profiles: - default stateful: false description: "" My system is using a squashfs root with an ext4 backed overlayfs.
  3. Jira closed, talk about speedy service! I am emerging the package now!
  4. raised: https://bugs.funtoo.org/browse/FL-4844
  5. Understood, I should say that I want to support dnscrypt and in fact I currently am using it; however, I recently updated my systems after March when that change was made and now I cannot install / update unbound. Walter
  6. Hi, I am unable to install unbound as I am getting the error saying there aren't any ebuilds to satisfy dev-libs/libsodium. I suppose it may be related to a recent ebuild change, but am wondering how to address this: emerge: there are no ebuilds to satisfy "dev-libs/libsodium[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?]" Walter
  7. I built NetworkManager with these settings: net-misc/networkmanager -dhclient -ppp -wext (I rebuilt it with -dhcpcd and have the same issue, and also ensure that my kernel had support for wireless extensions). However, I came across this bug and this post: https://bugs.funtoo.org/browse/FL-2372 The segfault: NetworkManager segfault at 8 ip 00007fa89e102e16 sp 00007fff51f34be8 error 4 in libc-2.23.so[7fa89e084000+18e000] The interesting thing is that this issue is tied to shorewall. Whenever I start my shorewall, I get this segfault. I only get this issue with this particular device (router) and not my other devices (workstations). The rulesets are different between my workstations and my router so that may be why I don't experience this issue on those devices. Still though, I find it odd that shorewall or iptables would cause some sort of issue with NetworkManager. I just reverted back to 1.4.4-r1 and will use that until I can sort out this issue with 1.10.2.
  8. I am unable to reproduce this as I did this on another machine and didn't record the entire sequence of events. I will mark this as closed.
  9. new kits, master branch [SOLVED]

    I am marking this as solved as editing /etc/ego.conf works and is simple enough for me.
  10. new kits, master branch [SOLVED]

    I am just editing /etc/ego.conf, this works fine for me.
  11. How would I automate testing a system?

    With the advent of virtualization, I wouldn't actually do these things, they would be simulated. I mean, there is no way Google or ... Microsoft manually test their products. Maybe there is some proprietary product that does this testing. It isn't whether I have issues with these things, it is whether I *COULD* have issues with these things and not know about it. I'd rather know when I build my system that something is broken so I could just not upgrade.
  12. [Off] Plymouth Theme

    I like the style of the anime one, that is really great. These look good, by chance are you an F1 fan? It'd be awesome to take another concept such as F1 and do what you did with the anime one for that, or something else linux-related.
  13. Hi all, I suspect I am having permissions problems with overlayfs. 1. created a file (as root) 2. ls -l <file> 3. confirmed the file is owned by root 4. ran unshare -r <some executable> - output indicates file as being owned by nobody or 65534 even though ls -l confirms it is owned by root 5. ls -l <file> still shows file is owned by root Lastly, I confirmed in /rw/<path-to-file> that the permissions are the same as the file I created. Why is unshare seeing different permissions and how do I see what it sees?
  14. How would I automate testing a system?

    Well, yes, stuff generally works; however, when I need to print or something I haven't done in a year, it may not work and chasing down the problem when I need it to work is bothersome. And, by then it would be nearly impossible to see what change may have caused it. It might turn out that an application configuration needs to be changed. If all of that stuff could be simulated, then once I have the activity captured where I could replay it later, then I would have a guarantee that a new build is good before I actually decide to reboot to it. It is the same reason we have kits.
  15. How would I automate testing a system?

    That doesn't answer how I would test a linux image (where an image is an ISO ...). Sure, whatever I ultimately would invoke could be initiated by this, but I'm looking for the tool that would simulate network traffic, someone logging in, plugging in a monitor, etc. I would imagine I could hack together a bunch of scripts to do stuff in virtualbox, but that is sort of limited I would imagine and tied to virtualbox. Even then, I'd probably have to code in C or something.
×