Re: [lxc-users] TTY issue
How do you rsync over SSH when all you have is a Plain Old FTP server to connect to? Maybe there is something I need to learn. On Sat, Nov 18, 2017 at 5:08 PM, Andrey Repinwrote: > Greetings, Saint Michael! > > > I need to do an rsync of hundreds of files very morning. The least > complex > > way to achieve that is to do an rsync with some parameters that narrow > down what files I need. > > Is there a better way? > > rsync over a network mount is the WORST POSSIBLE SOLUTION EVER. > Use normal rsync over SSH, it will be much faster, even if you do checksum > syncs. > > > -- > With best regards, > Andrey Repin > Sunday, November 19, 2017 01:07:34 > > Sorry for my terrible english... > > ___ > lxc-users mailing list > lxc-users@lists.linuxcontainers.org > http://lists.linuxcontainers.org/listinfo/lxc-users > ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
Re: [lxc-users] TTY issue
Greetings, Saint Michael! > I need to do an rsync of hundreds of files very morning. The least complex > way to achieve that is to do an rsync with some parameters that narrow down > what files I need. > Is there a better way? rsync over a network mount is the WORST POSSIBLE SOLUTION EVER. Use normal rsync over SSH, it will be much faster, even if you do checksum syncs. -- With best regards, Andrey Repin Sunday, November 19, 2017 01:07:34 Sorry for my terrible english... ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
Re: [lxc-users] TTY issue
Let me try that On Sat, Nov 18, 2017 at 9:13 AM, Marat Khaliliwrote: > On 18/11/17 17:10, Saint Michael wrote: > > Yes, of course. It works but only if autodev=0 > That is the issue. > > > Even as: > > lxc.hook.autodev = sh -c 'mknod ${LXC_ROOTFS_MOUNT}/dev/fuse c 10 229' > > ? > > > -- > > With Best Regards, > Marat Khalili > > ___ > lxc-users mailing list > lxc-users@lists.linuxcontainers.org > http://lists.linuxcontainers.org/listinfo/lxc-users > ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
Re: [lxc-users] TTY issue
On 18/11/17 17:10, Saint Michael wrote: Yes, of course. It works but only if autodev=0 That is the issue. Even as: lxc.hook.autodev = sh -c 'mknod ${LXC_ROOTFS_MOUNT}/dev/fuse c 10 229' ? -- With Best Regards, Marat Khalili ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
Re: [lxc-users] TTY issue
Yes, of course. It works but only if autodev=0 That is the issue. On Sat, Nov 18, 2017 at 9:06 AM, Marat Khaliliwrote: > On 16/11/17 18:50, Saint Michael wrote: > > The issue is with fuse, that is why I keep > lxc.autodev=0 > if I do not, if I set it to 1, then fuse does not mount inside a > container. I need fuse, for I mount an FTP server inside the container. > So I am caught between a rock and a hard place. > I akready asked about this contradiction on the LXC developers list. > > BTW, did you try: > > mknod /dev/fuse c 10 229 > > ? > > -- > > With Best Regards, > Marat Khalili > > ___ > lxc-users mailing list > lxc-users@lists.linuxcontainers.org > http://lists.linuxcontainers.org/listinfo/lxc-users > ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
Re: [lxc-users] TTY issue
On 16/11/17 18:50, Saint Michael wrote: The issue is with fuse, that is why I keep lxc.autodev=0 if I do not, if I set it to 1, then fuse does not mount inside a container. I need fuse, for I mount an FTP server inside the container. So I am caught between a rock and a hard place. I akready asked about this contradiction on the LXC developers list. BTW, did you try: mknod /dev/fuse c 10 229 ? -- With Best Regards, Marat Khalili ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
Re: [lxc-users] TTY issue
On 18/11/17 14:46, Saint Michael wrote: I need to do an rsync of hundreds of files very morning. The least complex way to achieve that is to do an rsync with some parameters that narrow down what files I need. Is there a better way? On Fri, Nov 17, 2017 at 11:43 PM, Andrey Repin> wrote: Was there the need for it? Really? I feel like you've dug the grave for yourself with this config. I understand the need, but not the solution. I also have some remote mounts (SMB, WebDAV...) that I'd like to rsync but don't want to mount on host. However, I my case I had to create "true" kvm-based VM for it. I'd like to learn a clean way to do it in LXC container without problems like OP encountered. -- With Best Regards, Marat Khalili ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
Re: [lxc-users] TTY issue
I need to do an rsync of hundreds of files very morning. The least complex way to achieve that is to do an rsync with some parameters that narrow down what files I need. Is there a better way? On Fri, Nov 17, 2017 at 11:43 PM, Andrey Repinwrote: > Greetings, Saint Michael! > > > lxc.mount.entry = proc proc proc nodev,noexec,nosuid 0 0 > > lxc.mount.entry = sysfs sys sysfs defaults 0 0 > > lxc.mount.entry = /cdr cdr none bind 0 0 > > lxc.mount.auto = cgroup:mixed > > lxc.tty = 10 > > lxc.pts = 1024 > > lxc.cgroup.devices.deny = a > > lxc.cgroup.devices.allow = c 1:3 rwm > > lxc.cgroup.devices.allow = c 1:5 rwm > > lxc.cgroup.devices.allow = c 5:1 rwm > > lxc.cgroup.devices.allow = c 5:0 rwm > > lxc.cgroup.devices.allow = c 4:0 rwm > > lxc.cgroup.devices.allow = c 4:1 rwm > > lxc.cgroup.devices.allow = c 1:9 rwm > > lxc.cgroup.devices.allow = c 1:8 rwm > > lxc.cgroup.devices.allow = c 136:* rwm > > lxc.cgroup.devices.allow = c 5:2 rwm > > lxc.cgroup.devices.allow = c 254:0 rwm > > lxc.cgroup.devices.allow = c 10:137 rwm # loop-control > > lxc.cgroup.devices.allow = b 7:* rwm# loop* > > lxc.cgroup.devices.allow = c 10:229 rwm #fuse > > lxc.autodev = 0 > > lxc.aa_profile = unconfined > > lxc.cap.drop= > > lxc.network.type = phys > > lxc.network.flags = up > > lxc.network.link = eth6 > > lxc.network.name = eth0 > > lxc.network.ipv4 = 0.0.0.0/27 > > lxc.network.type = macvlan > > lxc.network.flags = up > > lxc.network.link = eth3 > > lxc.network.name = eth1 > > lxc.network.macvlan.mode = bridge > > lxc.network.ipv4 = 0.0.0.0/24 > > > lxc.start.auto = 1 > > lxc.start.delay = 5 > > lxc.start.order = 0 > > lxc.rootfs = /data/iplinkcdr/rootfs > > lxc.rootfs.backend = dir > > lxc.utsname = iplinkcdr > > Was there the need for it? Really? > I feel like you've dug the grave for yourself with this config. > > > -- > With best regards, > Andrey Repin > Saturday, November 18, 2017 07:42:06 > > Sorry for my terrible english... > ___ > lxc-users mailing list > lxc-users@lists.linuxcontainers.org > http://lists.linuxcontainers.org/listinfo/lxc-users > ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users