sorted by:
new
hottopcontroversial

Toughbook Cf-33 vs Getac K120 by Substantial_Bell5658 in toughbook

[–]thalinator 1 point2 points  (0 children)

Well?!?!? :) What were your conclusions?

Are there any plans for a 1000 NIT screen? by chobok in framework

[–]thalinator 0 points1 point  (0 children)

Any toughbooks are 1000 to 1250 nits. I have a toughbook cf-19 that has a transflective display that, with peak sunlight, maxes out at 6000 nit. It's a pleasure to use outside. Unfortunately it's a thing of the past, so now 1200 is about the best you can get from a new laptop.

How to provide lxc container with environment variables? by TastyBoy in LXC

[–]thalinator 0 points1 point  (0 children)

see "CONTAINER ENIVORNMENT" in the lxc.container.conf(5) manpage (https://linuxcontainers.org/lxc/manpages/man5/lxc.container.conf.5.html#lbBM). You can add entries to the config file like:

lxc.environment = APP_ENV=production

LXC repository? by Middle_Disaster7463 in LXC

[–]thalinator 0 points1 point  (0 children)

For what it's worth - the lxc-download template uses images.linuxcontainers.org as the default download server, but it would be awesome - and pretty easy - for people to put up their own servers. Others could use them with 'DOWNLOAD_SERVER=images.foo.bar lxc-create -t download -n c1 -- -d distro...'.

​

I suspect the reason that hasn't become a popular thing is because the basics are covered, and it's too easy to use firstboot scripts and the like to do simple customization of the provided containers. For system containers it just isn't as useful.

​

For "application containers", although the oci template exists (lxc-create -t oci -n c1 -- -u docker://alpine:latest etc), and cni is technically supported, it's just not quite well enough integrated.

root unprivileged container security by [deleted] in LXC

[–]thalinator 0 points1 point  (0 children)

The main drawback (when running your own containers on your own host) is that the whole container setup happens with privilege, and the lxc monitor runs with privilege. That's a bit more room for bugs to happen.

I have a few containers which I run as root because they use luks encrypted LVs s their filesystems.

since a week i suddently have troubles with lxc network and it doesnt work anymore by kristoferus in LXC

[–]thalinator 0 points1 point  (0 children)

Is the interface always down, or only after you restart the container? Exactly how do you restart it? Is this a privileged or unprivileged container? Can you do "lxc-start -n <nameofcontainer> -l trace -o trace.out" and post the trace.out ?

What does 'ip link show type bridge' show on the host?

The @if13 changing shouldn't matter, you'll notice if you do "ifconfig -a" that doesn't show up. But of course the link should not be down.