Search results for query: lxc

  1. J

    Remote Migration with Shared Storage not working?

    ...then you can't use your NFS share on your NAS and you won't have migration or failover like with a cluster. Instead you would replicate the vms/lxcs from one node to the other and would be able to launch them in case one node gets lost: https://pve.proxmox.com/wiki/PVE-zsync Another option...
  2. fstrankowski

    Proposal to add a Notes option to the GUI.

    You highlighted two different types of notes. One are notes for backups, the other one are notes bound to VM/LXC which are storaged at the top of your VM/LXC configuration file prefixed with "###" for each line.
  3. B

    LXC cannot connect to network in default config

    Hi Jacob, that basically looks all right, so the troubleshooting might be a little bit more complex. mhm, one think I noticed in the lxc config is the activated firewall for the container. This should basically not influence anything, as long as the firewall for host and cluster are not active...
  4. H

    NVIDIA RTX 3060 GPU Passthrough - RmInitAdapter failed (0x25:0xffff:1601) on H170 Chipset

    Nope, I went on and created an LXC container in proxmox instead, no need to passthrough the GPU as a LXC container has access to GPU directly.
  5. fba

    Dokumentation zum Download für Claude Proxmox Skill

    Hallo, ich dachte bisher, in die md-Datei muss eine Beschreibung der Infrastruktur rein, Guards, Workflows usw. Die ganzen Basis-Befehle sollte Claude doch schon aus seinem Trainingsmaterial kennen. Wenn ich eine freundliche AI frage, erhalte ich nach wenigen Prompts schon sowas, reicht Dir das...
  6. J

    LXC cannot connect to network in default config

    ...scope global eth0 valid_lft forever preferred_lft forever inet6 fe80::be24:11ff:fe3e:ca5c/64 scope link valid_lft forever preferred_lft forever The ip of my router is 192.168.0.1 My subnet mask is 255.255.255.0 My router cannot see the lxc but can see the host Thanks!
  7. S

    LXC suddenly wont start after the node crashed

    ...onboot: 0 ostype: debian rootfs: local:105/vm-105-disk-0.raw,size=8G startup: order=1 swap: 0 unprivileged: 1 lxc.cgroup2.devices.allow: c 10:200 rwm lxc.mount.entry: /dev/net/tun dev/net/tun none bind,create=file The systlog complains about not being able to mount the filesystem but fsck...
  8. Impact

    Nvidia install for LXC

    Well considering that the script requires an existing CT I'd say it does. I'm not really a fan of manually editing the config file but I consider this the best method for NVIDIA cards and there doesn't seem to be CLI support for adding lxc. specific options.
  9. S

    Nvidia install for LXC

    ...it looks like a permission issue, but not sure how to fix that. Didn't want to try something and make things wrose :) root@vhs01:/etc/pve/lxc# pct start 914 --debug run_buffer: 571 Script exited with status 1 lxc_setup: 3935 Failed to run mount hooks do_start: 1274 Failed to setup...
  10. S

    Nvidia install for LXC

    @Impact, thanks for the quick response. Here you go.. root@vhs01:/etc/pve/lxc# pct start 914 --debug run_buffer: 571 Script exited with status 1 lxc_setup: 3935 Failed to run mount hooks do_start: 1274 Failed to setup container "914" sync_wait: 34 An error occurred in another process...
  11. Impact

    Nvidia install for LXC

    Share pct start 914 --debug and pct config 914. With the NVIDIA hook method you do not need lxc.mount* or dev* which I'm guessing you use.
  12. B

    LXC cannot connect to network in default config

    Hi Jacob, you posted the LXC configuration with the dhcp setup, can you add the one with the static ip address assignment? And maybe also add the routes the container is aware of and the state of the interfaces (host and LXC), with the static setup? ## ip routes ip route ## interfaces...
  13. S

    Nvidia install for LXC

    ...driver install, as I already did that, but did install the toolkit on the host. Should I go ahead and run the .run scripts? root@vhs01:/etc/pve/lxc# pct reboot 914 run_buffer: 571 Script exited with status 1 lxc_setup: 3935 Failed to run mount hooks do_start: 1274 Failed to setup container...
  14. U

    Proxmox LXC container losing IP on node-reboot/container-reboot/HA-Failover

    Hi all, Proxmox VE 9.1.4 4 Nodes, ceph, HA All network addresses are static. As the title suggests, I've experienced on multiple containers in my cluster the container network interfaces losing their IP on a reboot, failiver, or node reboot. The only way so far to fix, is to fully remove...
  15. J

    LXC cannot connect to network in default config

    ...bridge-ports enp1s0 bridge-stp off bridge-fd 0 source /etc/network/interfaces.d/* cat /etc/pve/nodes/localhost124/lxc/100.conf returns arch: amd64 cores: 1 hostname: CT100 memory: 512 net0: name=eth0,bridge=vmbr0,firewall=1,hwaddr=BC:24:11:3E:CA:5C,ip=dhcp,type=veth ostype...
  16. S

    Tool for creating fancy notes to Proxmox VM/LXC:s https://github.com/Snille/Proxmox-Notes

    Tool for creating fancy notes to Proxmox VM/LXC:s https://github.com/Snille/Proxmox-Notes
  17. V

    Start additional service when oci lxc container starts

    I just found out, that this is possible via Proxmox LXC hookscripts and pct exec Thank you, Volkmar
  18. V

    Start additional service when oci lxc container starts

    In oci images, there is no rc-service... Is there something like a Hook script which gets called at startup? How can I make sure, a certain command is started in case of container start? Example use case: A container based on a docker images needs to provide a samba share, which is not part of...
  19. B

    Proxmox 9.1.5 breaks LXC mount points?

    me2: many thanks for fixing this - pve-container 6.1.0 did not work but 6.1.1 fixed the problem for me (using "mpX: ... ro=1" mounts within the lxc config here). Yet while I agree with Johannes S and hnguk that proxmox basically did fine here because this bug did not hit the enterprise repos...
  20. H

    PBS cannot restore large disk from S3

    ...pull full bandwidth. Originally PBS had 8GB and 4c, along with only a 2TB cache disk for S3. During this time I could backup small (and large) LXC containers without issue, and could create the backup of my VM in S3 of ~4TB. Restoring LXC containers (16GB at most each) worked just fine. When...