similar to: Container setup?

On 7/3/19 8:21 AM, Sven Schwedas via samba wrote: > Though I'm not sure if docker is the right tool for the job; samba as a > fat daemon running a bazillion subprocesses orchestrated by a persistent > database that's very sensitive to instances leaving and joining the > domain seems the antithesis to docker's philosophy. > Docker would be a terrible choice for this;

> * What are pros and cons of container vs. VMs? Same as any other containerized setup. We've been running our Samba DCs and file servers in nspawn containers (similar to LXC) for a couple of years, no container-specific issues yet. Though I'm not sure if docker is the right tool for the job; samba as a fat daemon running a bazillion subprocesses orchestrated by a persistent database

On 7/4/19 12:49 PM, Joachim Lindenberg wrote: > * I am not (yet) familiar with LXD or nspawn. Do you have any pointer on how Samba DC works with LXD? > I've only used LXD for containerizing web applications so far.

Hi Patrick, thanks for the pointers. I tried today, and while it was easy to start my first container, I am not really happy with LXD, exactly for the reason St?phane gives in https://stgraber.org/2016/03/11/lxd-2-0-introduction-to-lxd-112/ "How does LXD relate to Docker/Rkt?"... what I really like about docker and docker-compose is, that it encourages to separate code from data and

Hi, I noticed that libvirt-lxc will be deprecated for RedHat: "Future development on the Linux containers framework is now based on the docker command-line interface. libvirt-lxc tooling may be removed in a future release of Red Hat Enterprise Linux (including Red Hat Enterprise Linux 7) and should not be relied upon for developing custom container management applications." -

I have a container rootfs that I use to keep all work-related stuff. This container was originally created by lxd (which creates all containers for use with user namespacing), but now I decided to start using libvirt for container management since I already use it for virtual machines, which will spare me from dealing with multiple hypervisor technologies. I managed to create a working domain xml

Dear all, I'm moving my first baby steps with libvirt-lxc trying to convert over from an LXD installation and one of the hurdles is putting together an image. All the examples I found about libvirt-lxc refer to running /bin/sh in a container, almost as if it was docker, as opposed to run a "full system" like I've been doing with lxd. Also virt-install, often referred in libvirt

Hello Patrick, >On 7/3/19 8:21 AM, Sven Schwedas via samba wrote: >> Though I'm not sure if docker is the right tool for the job; samba as a >> fat daemon running a bazillion subprocesses orchestrated by a >> persistent database that's very sensitive to instances leaving and >> joining the domain seems the antithesis to docker's philosophy. >>

After reading the instructions at https://wiki.samba.org/index.php/Time_Synchronisation, I still have questions about how samba interacts with nptd. The issue is that LXD doesn't want containers setting the time and so won't start ntpd at container startup even though it's enabled in systemd. The host does sync it's time with a national time server, so we can assume that the

Hi Sven, Ok, before i back to my packaging, i reviewed the changes. You still missed a bit but it looks much better already, your completely there, but we will get there. And you really need to be more precise, why im telling that... Well the review. ( thats not all, im still reviewing the base only) ... https://up.tao.at/u/samba/graz-file.info2.txt Checking file:

On Monday, August 7, 2023 6:05:03 AM EDT Andrew Bartlett via samba wrote: > https://github.com/samba-in-kubernetes > Andrew, thanks a bunch for pointing people to our org! I really appreciate it. More below... > On Mon, 2023-08-07 at 11:08 +0200, Joachim Lindenberg via samba wrote: > > Hello Anantha, Michael, > > IIRC this is somewhat optimistic or a secret sausage. For

On Wed, 9 Jan 2019 at 10:51, Rowland Penny via samba <samba at lists.samba.org> wrote: > On Wed, 9 Jan 2019 10:24:40 +0100 > "L.P.H. van Belle via samba" <samba at lists.samba.org> wrote: > > > What Marco and Robert already did say. > > > > This is what i mean ( and Robert ). Marco's option to disable though > > kernel is also an option.

On 2015-11-18 19:41, Warren Young wrote: > On Nov 18, 2015, at 1:20 PM, Kwan Lowe <kwan.lowe at gmail.com> wrote: try systemd-nspawn and use it instead of virtualizing, will save you some bits of memory.

> Keytabs look reasonable, as far as I can see, but why does > graz-dc-sem have the same SPN output as graz-dc-1b in > addition to its own? A snapshotted server/cloned server? I dont know but thats not correct. I suggest, cleanup the DS with FSMO roles. Then remove a failty server and re-add it as a new installed DC. ( the good DS with FSMO) First backup:

On Thu, Jan 30, 2014 at 04:34:04PM +0530, Kashyap Chamarthy wrote: > On 01/30/2014 03:58 PM, Richard W.M. Jones wrote: > >>> - `make -k check` is still running as I write this, albeit > >>> a bit slow. > >> > >> This just finished (in the container): > >> > >> [. . .] > >> grep -v -E

Today's episode of "why is AD break", brought to you by: > [2017/09/05 10:17:06.015617, 3] ../source4/auth/gensec/gensec_gssapi.c:613(gensec_gssapi_update) > Server GC/graz-dc-1b.ad.tao.at/ad.tao.at is not registered with our KDC: Miscellaneous failure (see text): Server (GC/graz-dc-1b.ad.tao.at/ad.tao.at at AD.TAO.AT) unknown > [2017/09/05 10:17:06.015717, 0]

On Fri, May 05, 2017 at 10:21:05AM +0200, Sven Schwedas wrote: > On 2017-05-05 10:09, Volker Lendecke wrote: > > On Fri, May 05, 2017 at 09:42:47AM +0200, Sven Schwedas via samba wrote: > >>> root 9988 0.8 59.4 1571936 606488 ? S Apr26 114:41 /usr/sbin/samba > > > > Can you post /proc/9988/smaps somewhere? > > Sure,

/etc/hostname:villach-file /etc/hosts:# The following lines are desirable for IPv6 capable hosts /etc/hosts:::1 localhost ip6-localhost ip6-loopback /etc/hosts:ff02::1 ip6-allnodes /etc/hosts:ff02::2 ip6-allrouters /etc/hosts:127.0.0.1 localhost /etc/hosts:192.168.16.214 villach-file /etc/krb5.conf:[libdefaults] /etc/krb5.conf: default_realm = AD.TAO.AT /etc/krb5.conf: dns_lookup_realm = true

On Thu, Jan 30, 2014 at 05:07:23PM +0530, Kashyap Chamarthy wrote: > On 01/30/2014 04:38 PM, Daniel P. Berrange wrote: > > [. . .] > > >> > >> Despite reading from the `systemd-nspawn` man page: > >> > >> ". . .kernel modules may not be loaded from within the container." > >> > >> I purposefully tried from inside the

Hi Marco, anybody, > + must be 'privileged' container (no unprivileged ones) I have seen containers with and without calling for being privileged, but you never know without trying and testing carefully... Googling I found https://github.com/lxc/lxd/issues/3442#issuecomment-312560949 but I am not really clear about the conclusion. Does it really have to be privileged? Thanks & Best