Error creating lxc container on -current

brobr · 11-12-2021, 06:44 PM

First time I tried containers as well ;-)
Looks I got as far you, but using dhcp='yes' and lxc-4.0.11 etc. of current (as of Thursday).

Code:

bash-5.1$ sudo lxc-ls --fancy
NAME STATE   AUTOSTART GROUPS IPV4       IPV6 UNPRIVILEGED 
s6   RUNNING 0         -      10.0.3.125 -    false

Did you try ping (as suggested in https://docs.slackware.com/howtos:misc:lxc)? That worked at my end:
From inside the container:

Code:

rob@s6:~$ ping www.aileenbannatyne.co.uk
PING aileenbannatyne.co.uk (5.77.32.213) 56(84) bytes of data.
..
13 packets transmitted, 13 received, 0% packet loss, time 12014ms

from a terminal outside to the container:

Code:

bash-5.1$ ping 10.0.3.125
..
6 packets transmitted, 6 received, 0% packet loss, time 5100ms

not much more in there to go on-line with due to the minimal install...

glorsplitz · 11-13-2021, 11:29 AM

went about redoing everything as there is lxc-4.0.11, seems to working now

looks like I'm where you're at, time to try "slackpkg install slackware64"

glorsplitz · 11-13-2021, 11:55 AM

not sure how to continue, from slackdocs doing "slackpkg install slackware64"

Quote:

slackpkg install slackware64

The package list is missing.
Before you install|upgrade|reinstall anything you need to run:

# slackpkg update

Quote:

slackpkg update
ERROR: Verification of the gpg signature on CHECKSUMS.md5
failed!

Quote:

slackpkg update gpg

Getting key from https://www.slackware.com/infra/keys/GPG-KEY

using mirror from lxc-create

Quote:

http://mirrors.us.kernel.org/slackwa...ware64-current

Quote:

slackpkg update
ERROR: Verification of the gpg signature on CHECKSUMS.md5
failed!

Quote:

PRETTY_NAME="Slackware 15.0 x86_64"

glorsplitz · 11-13-2021, 07:20 PM

slackpkg issue solved, seems NOT use mirror from lxc-create but use this one http://ftp.slackware.com/pub/slackwa...are64-current/ which isn't in my slackware64-current mirrors?

Quote:

slackpkg install slackware64

running now, will post back after dust settles

EDIT:dust has settled, now have a 13.5 GiB slackware64-current container.

slac-in-the-box · 11-20-2021, 04:03 PM

Howdy LXC Slackers:

FWIW:

Code:

root@darkstar:~# date && uname -r && ls /var/lib/pkgtools/packages/lxc*
Sat Nov 20 13:53:25 PST 2021
5.15.3
/var/lib/pkgtools/packages/lxc-4.0.11-x86_64-3

Code:

root@darkstar:~# grep elflibs /usr/share/lxc/templates/lxc-slackware
aaa_elflibs

root@darkstar:~# slackpkg file-search aaa_elflibs

Looking for aaa_elflibs in package list. Please wait... DONE

No packages contains "aaa_elflibs" file.

Conclusion: safe to remove aaa_elflibs from lxc-slackware

brobr · 11-20-2021, 04:37 PM

Hmm, trying to run a gui acc. to howtos:misc:lxc but it ends with:

Code:

rob@s6:~$ ssh -Y rob@10.0.3.44 gimp
(rob@10.0.3.44) Password: 
Warning: No xauth data; using fake authentication data for X11 forwarding.
connect /tmp/.X11-unix/X0: No such file or directory
Cannot open display:

/tmp/.X11-unix/ exists, but X0 doesn't

an attempt with another, Qt-based program began with the same error:

Code:

connect /tmp/.X11-unix/X0: No such file or directory
qt.qpa.xcb: could not connect to display localhost:10.0
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
error: XDG_RUNTIME_DIR not set in the environment.

What have I missed setting up?

(PS, s6 is the container from which the gui is run)

EDIT

found this advice on https://bbs.archlinux.org/viewtopic.php?id=200704 :
mount /tmp/.X11-unix as read-only

Code:

lxc.mount.entry = /tmp/.X11-unix tmp/.X11-unix none bind,ro,optional,create=dir

but still gives "Cannot open display: "; /tmp/.X11-unix/ is still empty

avian · 11-21-2021, 02:24 AM

Quote:

Originally Posted by brobr

but still gives "Cannot open display: "; /tmp/.X11-unix/ is still empty

This might be very off track (apologies if so), but in your /etc/ssh/sshd_config (within the container) have you enabled X11 forwarding? For example changing these two lines to be similar to the following?

Code:

X11Forwarding yes   
X11DisplayOffset 10

glorsplitz · 11-21-2021, 09:48 AM

brobr, that's funny, I decided to do the same, tried glxgears, kcalc, couple simple things and they worked.

Saw your post, tried gimp, didn't work, then tried glxgears, kcalc again and they didn't work, not sure what happened.

Thanks avian, we did what was said from the link brobr last posted, where it says "Running GUI Applications", didn't try "X11DisplayOffset 10".

brobr · 11-21-2021, 01:58 PM

Quote:

Originally Posted by avian

This might be very off track (apologies if so), but in your /etc/ssh/sshd_config (within the container) have you enabled X11 forwarding? For example changing these two lines to be similar to the following?

Code:

X11Forwarding yes   
X11DisplayOffset 10

Thanks, avian; like glorsplitz said the `X11DisplayOffset 10` was not set. Anyway, enabling that did not help me. Had to restart X to test it (got temporarily /tmp/.X11/X0, but that has gone again).

EDIT: found another blog, GUI-From-an-LXC-Container-on-the-Host that seemed relevant; it also mentions the 'ro' addition to the `lxc.mount.entry = /tmp/.X11-unix` line in the config file, needed to keep the /tmp/.X11-unix/X0.
Then, when following the sequence sketched out in that blog, the display is found for the container and for the host via:

Code:

#env | grep -i display 
env | grep DISPLAY

This works at my end only on the host (gives: 'DISPLAY=:0.0'); on the container nothing (while 'env' gives a lot of output)

brobr · 11-21-2021, 05:53 PM

Hmm, found on this bug report https://github.com/lxc/lxc/issues/1859 another way to start a gui:

This worked from host with xeyes, glxgears, gimp and jamulus -s as gui-app;-):

Code:

ssh user@containerIP
<passw>
DISPLAY=:0 <gui-app>

or from host,

Code:

ssh -Y user@containerIP DISPLAY=:0 <gui-app>
<passw>

From within the container the command 'DISPLAY=:0 <gui-app>' was enough.

For jamulus not to throw a "libGL error: MESA-LOADER: failed to retrieve device information" the following lines (from blog in previous post; control values via 'ls -l /dev/dri' ) needed to be in the lxc.config:

Quote:

lxc.cgroup.devices.allow = c 226:* rwm
lxc.mount.entry = /dev/dri/card0 dev/dri/card0 none bind,optional,create=file
lxc.mount.entry = /dev/dri/renderD128 dev/dri/renderD128 none bind,optional,create=file