SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I get this error when trying to create a Slackware64-current container:
Code:
chpasswd: error while loading shared libraries: libpam.so.0: cannot open shared object file: No such file or directory
Error creating container Slackware64-current
Adding pam to the minimal list of packages in /usr/share/lxc/templates/lxc-slackware fixes that problem. However, now I get this error:
Code:
chpasswd: (user root) pam_chauthtok() failed, error:
Module is unknown
chpasswd: (line 1, user root) password not changed
Error creating container Slackware64-current
As a guess, I tried adding krb5 and pam-krb5 (separately) to the list, but that didn't help. Anyone know which packages are needed for chpasswd to work correctly?
I'm having similar issues. I installed cracklib and libpwquality as suggested however, I'm not getting as far the error you have, I'm still getling the libpam error:
Code:
lxc-create -n test -t slackware --bdev dir
....
Configuring...
Adding an etc/fstab that must be modified later with the
full path of the container's rootfs if you decide to move it.
chpasswd: error while loading shared libraries: libpam.so.0: cannot open shared object file: No such file or directory
Error creating container test
I also note that --bdev btrfs seems not to work either, with different errors. No idea if that is related.
I'm having similar issues. I installed cracklib and libpwquality as suggested however, I'm not getting as far the error you have, I'm still getling the libpam error:
Code:
lxc-create -n test -t slackware --bdev dir
....
Configuring...
Adding an etc/fstab that must be modified later with the
full path of the container's rootfs if you decide to move it.
chpasswd: error while loading shared libraries: libpam.so.0: cannot open shared object file: No such file or directory
Error creating container test
I also note that --bdev btrfs seems not to work either, with different errors. No idea if that is related.
That was the error I got before adding pam. Did you do that?
That was the error I got before adding pam. Did you do that?
OK. Should have read the first post more carefully. I installed cracklib and libpwquality on the host system (but I assume they should already have been there) and I missed the bit about pam.
So I updated the template to add pam, cracklib and libpwquality, and I get the same, I thnk, as the other poster.
Code:
Configuring...
Adding an etc/fstab that must be modified later with the
full path of the container's rootfs if you decide to move it.
chpasswd: (user root) pam_chauthtok() failed, error:
Authentication token manipulation error
chpasswd: (line 1, user root) password not changed
Error creating container test
Well, I've got a workaround. With the following changes to /usr/share/lxc/templates/lxc-slackware, I can get a working container. Basically, I add the a, ap, d, k, l, and n groups to the installer. It's no longer minimal, though, but that's okay for me because I wanted a full install anyway. But I think this confirms that the problem is missing packages in addition to the ones that have already been identified (rather than a configuration issue like permissions), but I don't know which ones.
Code:
--- lxc-slackware 2020-01-02 15:21:06.000000000 -0500
+++ lxc-slackware.new 2020-06-29 15:08:09.821555944 -0400
@@ -95,8 +95,8 @@
for clear_device in ${DEV}/null ${DEV}/zero ${DEV}/random ${DEV}/urandom \
${DEV}/tty ${DEV}/console ${DEV}/tty0 ${DEV}/tty1 ${DEV}/tty2 ${DEV}/tty3 \
${DEV}/tty4 ${DEV}/tty5 ${DEV}/full ${DEV}/initctl ${DEV}/loop0 \
- ${DEV}/loop1 ; do
- rm -f $clear_device
+ ${DEV}/loop1 ${DEV}/pts ${DEV}/shm ${DEV}/ptmx ${DEV}/fd; do
+ rm -rf $clear_device
done
# Create initial set of devices:
mknod -m 666 ${DEV}/null c 1 3
@@ -237,6 +237,7 @@
bin
bzip2
coreutils
+cracklib
cyrus-sasl
db48
dcron
@@ -261,6 +262,7 @@
libcap-ng
libffi
libmnl
+libpwquality
libtasn1
libunistring
logrotate
@@ -272,6 +274,7 @@
openssh
openssl-solibs
p11-kit
+pam
pkgtools
procps-ng
sed
@@ -304,6 +307,7 @@
slackpkg -default_answer=n update
slackpkg install-template $TEMPLATE
+slackpkg install a ap d k l n
# add a slackpkg default mirror
echo "$MIRROR/$PKGMAIN-$release/" >> $ROOT/etc/slackpkg/mirrors
I just tested it and I spotted an issue with pam_securetty (as we seem to login from pts/0 using lxc-console): you can check if this is solves your issue editing /etc/securetty in the container (allowing login from pts)
Code:
sed -i "s|^#pts|pts|" $ROOT/etc/securetty
you should also have related errors in /var/log/secure if this is the case...
regarding the packages template for the container this is the new one I used here
it can be in your case that just libtirpc is needed.
BTW, here you can find a new version of the build script with the new template and the new init scripts (synced with the ones from Slackware current as today)
I just tested it and I spotted an issue with pam_securetty (as we seem to login from pts/0): you can check if this is solves your issue editing /etc/securetty in the container (allowing login from pts)
Code:
sed -i "s|^#pts|pts|" $ROOT/etc/securetty
you should also have related errors in /var/log/secure if this is the case...
regarding the packages template for the container this is the new one I used here
<snip>
it can be in your case that just libtirpc is needed.
BTW, here you can find a new version of the build script with the new template and the new init scripts (synced with the ones from Slackware current as today)
That worked. I didn't need to make any changes to pam_securetty in order to get it installed and apparently working. So to summarize, the following 4 packages need to be added to the list:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.