Where are .conf files located?

[circuitcat]

I'm running Proxmox 8.4.0 and have several VMs. One of them, I need to reset the password in-container via this guide. However, in the prox shell, when I enter "pct enter 106" it tells me

Configuration file 'nodes/prox/lxc/106.conf' does not exist

And in fact repeats that for every single VM I have. All of them will launch, so it clearly has a .conf file for them somewhere, but when I run "find . "106.conf"" it returns no results, and "ls" won't even show me a list of my current directory, let alone allow me to move to /nodes/prox/lxc via cd.

What am I missing here?

 

[Onslow]

Welcome, circuitcat!
To let us being able to help you, we need a detailed description of steps that you have done so far. Also, a quotation of the commands and their outputs.

 

[EllerholdAG]

PCT ist for lxc Containers. You we're talking about VMS, correct?
VMs you have to Change the PW in the VM itself. E. G. By booting into a Safe Mode

 

[Impact]

Or if you have the guest agent

qm guest exec VMID -- bash -c 'echo -e "root\nroot" | passwd'

 

[circuitcat]

PCT ist for lxc Containers. You we're talking about VMS, correct?
VMs you have to Change the PW in the VM itself. E. G. By booting into a Safe Mode

I see, alright. That is what I'm trying to do, boot into an Ubuntu VM. I just tried booting it and hitting "e" to hit the grub menu, unsurprisingly that didn't work. Is there a standard way to do this, or would I be better off rebuilding from the .iso? (While I'd rather not do that for time's sake there's no data at risk if I have to).

To @Impact's point I unfortunately do not have the guest agent enabled.

Re: @Onslow I basically only did the one command, "pct enter 106", and what I posted above is the response I got. Presumably because I was using the wrong process for a VM per Ellerhold.

 

[Onslow]

That is what I'm trying to do, boot into an Ubuntu VM. I just tried booting it and hitting "e" to hit the grub menu, unsurprisingly that didn't work.

What do you mean by "that didn't work"? I'm asking because this is a very general, imprecise statement.
It's too difficult to help unless you write what exactly have happened then.

Is there a standard way to do this, or would I be better off rebuilding from the .iso? (While I'd rather not do that for time's sake there's no data at risk if I have to).

Rebuilding should not be necessary.

Re: @Onslow I basically only did the one command, "pct enter 106", and what I posted above is the response I got. Presumably because I was using the wrong process for a VM per Ellerhold.

Now it's more understood.
I asked because you wrote "via this guide". But:
first: there are two guides at that link.
Second: the first of them contains two methods.
Third: at the beggining you wrote about a VM but later wrote pct command.
Fourth: you failed to write which steps you made.

Without a precise and complete description, trying to help is frustrating and too time-consuming.

 

[circuitcat]

What do you mean by "that didn't work"? I'm asking because this is a very general, imprecise statement.
It's too difficult to help unless you write what exactly have happened then.

Rebuilding should not be necessary.

Now it's more understood.
I asked because you wrote "via this guide". But:
first: there are two guides at that link.
Second: the first of them contains two methods.
Third: at the beggining you wrote about a VM but later wrote pct command.
Fourth: you failed to write which steps you made.

Without a precise and complete description, trying to help is frustrating and too time-consuming.

I rapidly tapped "e" during the boot process, which has dropped me into GRUB on other linux devices in the past, but there was no effect during the prox-boot; it simply booted to the login prompt as if I wasn't interacting at all.

I'm trying to essentially use the same process as the originally posted link describes for reseting the host password (drop into grub, set "linux /vmlinuz..." to "init=/bin/bash", then boot and run "mount -o remount,rw /" to then run "passwd", but I'm not sure if there's an alternate way to boot into grub when running as a VM.

 

[Onslow]

It should work very similar. You're trying in the "console" of the VM (in the web GUI), right?
If there was no effect after "e", maybe there was no "focus" on the console window or maybe the boot was quicker than yours hitting "e".

Anyway, if you don't manage to use boot of the VM itself, you can (in the VM settings) place an ISO image of some "live CD" system and proceed similarly to "Method 2".