podman pod create \
--name YOUR_POD_NAME \
-p 8080:8080
| The operation on file \\.\PhysicalDrive failed ... | |
| Fix: | |
| 1) Physical disk should be offline in the host OS. | |
| 2) Clear readonly attribute with diskpart | |
| ``` | |
| diskpart | |
| list disk | |
| select disk 5 |
This note explains the common issue of "notapplicable" results when running openSCAP and SCAP-Security-Guide on CentOS.
SCAP seems like it should be easy because it is "just XML". Then you dig into looking for a test and it gets confusing fast. So it is good to have some background.
SCAP (Security Content Automation Protocol) is actually a set of multiple standards and specifications that are used together to enable automatically testing hundreds of nerd settings. Let me emphasize that: SCAP is not a single XML specification -- SCAP is multiple standards and specs. Whenever you give "SCAP Content" to a scanner to check a system configurations you are giving the scanner multiple XML files representing multiple standards.
When I talk about Red Hat's involvement in RDO (http://openstack.redhat.com/) the question I often get is, "doesn't that undermine sales of RHEL OSP (Red Hat's paid OpenStack offering)?"
Well, it's complicated.
| " Don't try to be vi compatible | |
| set nocompatible | |
| " Helps force plugins to load correctly when it is turned back on below | |
| filetype off | |
| " TODO: Load plugins here (pathogen or vundle) | |
| " Turn on syntax highlighting | |
| syntax on |