11 mo. ago • 90%

some questions/ virt-manager/ proxmox/ debian

I am going to redo my server from scratch. I installed virt-manager hoping to build it in there and keep setup guide/notes for myself for when i move it to the server pc.

Im not fluent in linux speak so bare with me.

Does anyone know how I can reach the proxmox IP when its in a vm set up with virt-manager? I installed it with the default network adapter setting and it gave me 10.0.2.15 for the ip. I couldnt reach it from the main system or a debian vm. I deleted both the proxmox and debian vm's and will try again. Should I be using a different network mode in virt-manager? is it even possible to do what im trying to do?

I want to try out using proxmox with a debian vm instead of baremetal omv for docker. I was also thinking about using a VM of omv for my storage drives.

anyone have input on this stuff? I saw docker has a desktop app that seems pretty good so I was going to try that. Or would it be better to just install debian without a DE and use docker from the command line?

should i just use debian for the drive shares too? should i stick with smb?

does it even make sense for me to use proxmox? I figured it would be easier for me (personally) to keep things backed up. I like the idea of being able to create new vm's to experiment with without breaking my main/only server.

Thanks

9 comments

Unfortunately Proxmox doesn't use libvirtd, so Virt-Manager doesn't interact with it. It's designed entirely around using the web interface.

Your options here are to either stick with Proxmox without Virt-Manager, or use straight KVM. If you want a web interface for KVM, there's Cockpit, which is pretty decent for most basic tasks, but definitely a little lacking in advanced features, so you'll end up going to Virt-Manager for stuff like modifying virtual hardware. I think you can also use OpenStack as a web interface, but I've never played around with it myself.

Honestly, if you're a little newer to Linux I would probably stick with Proxmox, as it's a very well designed purpose built hypervisor.

For Docker, you'll want to deploy a VM and then setup Docker within the VM. Never run Docker from your hypervisor, it likes to fuck with IPtables in ways that break VM networking.

7
Seems like you’re nesting virtualization too much. Stick with 1 level of virtualization. If it’s a server, I’d use proxmox on bare metal. Its a server so split services per VM/container. Install OMV on its own VM. Another for docker, with docker services ran by a non root user.

4
Sounds like bridge mode is needed for the vm's network interface in virt.

I would say proxmox ve is easier to start with.

3
Install the proxmox iso directly on the hardware. Then setup a Debian without DE in a vm to run docker. Use Portainer to manage Docker containers.

Storage can then be assigned via Proxmox to the vm’s that need it.

1
- Excellent suggestion, although I would look at using Dockge instead of Portainer these days. It's very new and a little more feature limited, but it does a much better job of actually explaining how and why things are failing. If you're new at Docker then Portainer is a nightmare because all it does is scream "WRONG" and then storm off if you so much as put a single typo.
  
  3
  
  Perfect description of my experiences with portainer. I didn't know about dockge and it looks very promising! Thanks
  
  1
- This is what I do, but with alma instead of debian.
  
  Proxmox can run containers directly, but I haven't tried it yet.
  
  2
  
  Pretty sure Proxmox only supports LXC containers, not OCI
  
  1

You've viewed 9 comments.