cracklib | CrackLib Library and Dictionaries | Dictionary library

I have list of packages like this (it's bigger than this):

I have a docker container running where I want to install a package. Container is bebian based without Package Managers.

The output of cat /proc/version

I have a container I'm deploying to Kubernetes (GKE), and the image I have built locally is good, and runs as expected, but it appears that the image being pulled from Google Container Registry, when the run command is changed to pwd && ls returns the output shown here:

I am trying to add PAM support to my embedded Linux build. I am using a the Rocko version of the Yocto project. I added DISTRO_FEATURES_append += " pam" to my build. In my build I see the pam.d folder as expected. In my /lib/security folder I see many of the expected modules like pam_unix.so and pam_group.so. What I do NOT see is the pam_cracklib.so module. I looked at the BB recipe for pam given by the Rocko release and I see that it depends on cracklib and the supplied cracklib recipe is run.
I must be missing something basic. Why do I not see the pam_cracklib.so module available? I also verified it is not in some other folder.

I am having issues installing packer onto the EC2 machine. I have downloaded the Linux packer binary file on my Windows PC and uploaded it to the instance. I put it into the directory ~/packer_new, and have been trying two different ways for adding it to the path because it produces this error:

/usr/share/cracklib/pw_dict.pwd: Permission denied
/usr/share/cracklib/pw_dict: Permission denied

When I run just the packer command.

On the packer website, it states

To fix this, you can create a symlink to packer that uses a different name like packer.io, or invoke the packer binary you want using its absolute path, e.g. /usr/local/packer.

I have done the first part by creating a symbolic link using this command:

sudo ln -s packer_new/packer /usr/bin/packer.io

And when I run the packer command again, it still produces the same error. Am I supposed to be running a different command?

And the second way is to add the path to ~/.bash_profile:

export PATH=$PATH:~/packer_new/

Note that I also have another PATH variable in the bash_profile for bin: PATH=$PATH:$HOME/.local/bin:$HOME/bin, not sure if this will affect setting PATH to packer...

But by adding the path, it also produces the same error when running packer.

How can I fix this?

One more question, what does it mean when they say:

invoke the packer binary you want using its absolute path, e.g. /usr/local/packer.