dracut | dracut the event driven initramfs infrastructure | Microservice library
kandi X-RAY | dracut Summary
kandi X-RAY | dracut Summary
dracut the event driven initramfs infrastructure
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of dracut
dracut Key Features
dracut Examples and Code Snippets
Community Discussions
Trending Discussions on dracut
QUESTION
Getting crypto/fips/fips.c:153: OpenSSL internal error: FATAL FIPS SELFTEST FAILURE when
dracut-fips package is installed and sysctl -a shows crypto.fips_enabled = 1
Restriction: Can not disable dracut-fips
package or crypto.fips_enable
setting in my case.
How can I get cmake --version
working inside the container?
ANSWER
Answered 2022-Feb-22 at 09:42Found the solution
WHY this issue was coming:
Docker build (to create the image) was run on a machine (the other machine, where cmake was working inside the docker container)... i.e. where FIPS was not installed.
During the build step, Docker file was running
zypper install cmake
(or yum install cmake
).
As FIPS was disabled on the machine where docker image was built, cmake was installed in docker image, without understanding FIPS being enabled / dracut-fips being installed.
Then, when you copy this image and consume it on a machine where FIPS is actually ENABLED, then cmake was failing with that error mesg: crypto/fips/fips.c:153: OpenSSL internal error: FATAL FIPS SELFTEST FAILURE
--
Solution #1: Tag your docker image appropriately.
Summary:
PS: If you do install cmake using the above, then it'll only work on target machine where you run container, if that machine's FIPS is disabled or enabled at build time. i.e. if FIPS was enabled, you install cmake and run it on a machine where it's NOT same FIPS setting as the host, where image was built, then you'll be reading this post for help.
Better way in case you want to install cmake using the above package managers, would be, tag your docker image appropriately during image creation time i.e.:
docker build -t -fips-enabled ...
if FIPS is enabled
and
docker build -t -fips-disabled ...
if FIPS on that that machine is disabled.
That way, you can pick the correct docker image imagename-fips-enabled vs imagename-fips-disabled acc. to what your target machine FIPS setting is (where you'll actually perform docker run ...
using this image).
--
Solution #2: Don't use zypper (OpenSuse) or yum if you have RedHat container. and this solution is flexible in the sense, that it's independent of FIPS setting = 0 / 1 on the host, where image was built.
I didn't use zypper
/yum
to install cmake
inside Dockerfile
, but just grabbed cmake-3.18.2-Linux-x86_64.tar.gz bundle file.
Within Dockerfile, I simply extracted this .tar.gz file inside some directory.
Also I set export PATH:/path/where/I/installed/cmake-3.18.2../bin:/..some_other_paths:/...:/....
in Dockerfile inside RUN statement.
i.e.
RUN export PATH=/path/where/I/installed/cmake-3.18.2../bin:/...... && && && ... etc
, so it can find the extracted cmake 3.18.2 for any buil-time (cmake operations) and also SET the same PATH=/... variable as ENV PATH=/.... same value used during RUN for PATH
so at runtime, when the container runs, $PATH is all set for finding cmake
(3.18.2 version) rather than using any existing /usr/bin/cmake or some other shit
).
Dockerfile snapshot:
QUESTION
Yesterday we lost contact with 10 identically configured servers, after some investigation the conclusion was that a reboot after security updates had failed.
We have so far not been able to get any of the servers back online, but were lucky enough to be able to reinstall the instances without data loss.
I will paste the console log below, can anyone help me determine the root cause and perhaps give me some advice on if there is a better way to configure the server to make recovery easier (like getting past the "Press Enter to continue." prompt, that it seems to hang in).
The full log is too big for SO, so I put it on pastebin and pasted a redacted version below. I have removed the escape sequences that colorize the output and removed some double new lines, but besides that it is complete.
...ANSWER
Answered 2020-Oct-30 at 11:21Ok, shortly after posting we figured it out. Seems like a mount point has changed (I expect due to a linux kernel update) and we have not used the nofail option in /etc/fstab as described in the aws knowledge center, this caused the server to hang at boot.
Going forward we will also ensure we use UUID mounting so we are independent on the device naming in /dev/.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install dracut
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page