Selfhosted

40439 readers

733 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago

MODERATORS

some questions/ virt-manager/ proxmox/ debian (lemmy.ml)

submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/selfhosted

9 comments fedilink hide all child comments

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

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 2 points 1 year ago* (last edited 1 year ago) (2 children)

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.

[–] [email protected] 3 points 1 year ago (1 children)

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.

[–] [email protected] 1 points 1 year ago

Perfect description of my experiences with portainer. I didn't know about dockge and it looks very promising! Thanks

[–] SheeEttin 2 points 1 year ago (1 children)

This is what I do, but with alma instead of debian.

Proxmox can run containers directly, but I haven't tried it yet.

[–] [email protected] 1 points 1 year ago (1 children)

Pretty sure Proxmox only supports LXC containers, not OCI

[–] [email protected] 1 points 1 year ago* (last edited 1 year ago)

You could install docker with proxmox, it's just debian after all, then you could install portainer to visualize them. I just don't think it's a good practice to install docker directly on a hypervisor, too much risk to screw something up and then you may need to reinstall everything affecting all other VMs.

You could however install docker on a lxc. Not the easiest approach but less risky.

Edit: or Dockge in your case