Skip to content
This repository has been archived by the owner on Nov 2, 2024. It is now read-only.

Vaultwardeden - installation error #357

Closed
IT-BAPBAP opened this issue Jul 19, 2022 · 9 comments
Closed

Vaultwardeden - installation error #357

IT-BAPBAP opened this issue Jul 19, 2022 · 9 comments

Comments

@IT-BAPBAP
Copy link

HOST:
Proxmox 7.2-7
CPU - 4 x Intel(R) Core(TM) i5-7600K CPU @ 3.80GHz
PVE version - Linux 5.13.19-2-pve #1 SMP PVE 5.13.19-4

I tried to install Vaultwardeden LXE from the shell using a script:
bash -c "$(wget -qLO - https://github.com/tteck/Proxmox/raw/main/ct/vaultwarden-v3.sh)"

When executing the script, the following error occurs:

image

LXE was created and launched, but without Vaultwardeden

@tteck
Copy link
Owner

tteck commented Jul 19, 2022

I changed the default settings from 4vCPU to 2vCPU and 4096MiB ram to 2048MiB a couple of days ago but forgot to change what it actually shows (after noticing your Default Settings, fixed now).

Usually an error at building is a result of low resources, (you were using half of what the screen was showing) so try advanced settings and give it more resources.

@tteck
Copy link
Owner

tteck commented Jul 19, 2022

Just wondering, did you pin that kernel version or has it been awhile since you last rebooted?
Current: pve-manager/7.2-7/d0dd0e85 (running kernel: 5.15.39-1-pve)

@IT-BAPBAP
Copy link
Author

pin that kernel :)

@IT-BAPBAP
Copy link
Author

Strange.., I freed up all Proxmox resources and ran the installation script, but the error is the same.

image

@tteck
Copy link
Owner

tteck commented Jul 19, 2022

Let me run the script to make sure everything's ok

@IT-BAPBAP
Copy link
Author

Thank you very much). I'm sorry for my bad English :), I'm from Russia myself)

@tteck
Copy link
Owner

tteck commented Jul 19, 2022

I had forgotten how long that process was!
No issues here with the install

 __      __         _ _                         _            
 \ \ v3 / /        | | |                       | |           
  \ \  / /_ _ _   _| | |___      ____ _ _ __ __| | ___ _ __  
   \ \/ / _  | | | | | __\ \ /\ / / _  |  __/ _  |/ _ \  _ \ 
    \  / (_| | |_| | | |_ \ V  V / (_| | | | (_| |  __/ | | |
     \/ \__,_|\__,_|_|\__| \_/\_/ \__,_|_|  \__,_|\___|_| |_|

Using Default Settings
Using CT Type Unprivileged NO DEVICE PASSTHROUGH
Using CT Password Automatic Login
Using CT ID 111
Using CT Name vaultwarden
Using Disk Size 6GB
Using 2vCPU
Using 2048MiB RAM
Using Bridge vmbr0
Using Static IP Address DHCP
Using Gateway Address NONE
Using VLAN Tag NONE
 ✓ Using local for Template Storage.
 ✓ Using local-lvm for Container Storage.
 ✓ Updated LXC Template List
 ✓ LXC Container 111 was successfully created.
 ✓ Started LXC Container
 ✓ Setup Container OS
 ✓ Network Connected: 192.168.86.44 
 ✓ Updated Container OS
 ✓ Installed Dependencies
 ✓ Installed Rust
 ✓ Built Vaultwarden 1.25.1
 ✓ Downloaded Web-Vault v2022.6.2
 ✓ Created Service
 ✓ Customized Container
 ✓ Cleaned
 ✓ Set Container to Normal Resources
 ✓ Completed Successfully!

Vaultwarden should be reachable by going to the following URL.
         http://192.168.86.44:8000 

root@proxmox:~# 

But, it hammers on the CPU pretty good.

@tteck
Copy link
Owner

tteck commented Jul 19, 2022

Try advanced settings (you used default again) and give it more resources.

@IT-BAPBAP
Copy link
Author

And in truth, the problem was associated with a heavy load on the processor during installation, it helped to allocate 4 cores. Thank you very much!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants