matze/docs
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

[logseq-plugin-git:commit] 2024-07-19T15:44:44.459Z

Browse Source
This commit is contained in:
matze 2024-07-19 17:44:44 +02:00
parent 3a14c3ded0
commit 3273037f3e
1 changed files with 9 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
journals/2024_07_19.md
View File

@ -1,8 +1,14 @@
- #IAM #keycloak #SelfHosted
- Running Keycloak in Proxmox Image doesn't work out of the box
- ```
I had the same issue with running some RHEL 9 images in Podman on a Fedora Linux under Proxmox. RHEL 9 is checking this now for some reason.
- I had the same issue with running some RHEL 9 images in Podman on a Fedora Linux under Proxmox. RHEL 9 is checking this now for some reason.
The problem is caused by the underlying CPU architecture that Proxmox was telling Fedora that it had.
The problem was resolved very simply. When configuring the VM (or when the VM is in a stopped state) set the CPU architecture value to "host."
In Proxmox, if the machine is already provisioned you stop the server, open the Hardware setting, click Processors. Set the Type value to "host."
```
- Proxmox mount Client Partition (https://www.reddit.com/r/Proxmox/comments/e92mcz/can_i_access_vm_filesystem_from_the_host_shell/)
- ```
losetup --partscan /dev/loop0 /dev/zvol/tank/vms/vm-100-disk-1
fdisk -l /dev/loop0
mount /dev/loop0p2 /mnt
umount /mnt
losetup --detach /dev/loop0
```