Search results

root@pve1:~# ip addr 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host...

Just for practice, I made the change in the GUI: Which produced this in /etc/network/interfaces: allow-vmbr0 vlan88 iface vlan88 inet static address 10.0.10.20 netmask 255.255.255.0 ovs_type OVSIntPort ovs_bridge vmbr0 ovs_options tag=88...

This just in https://lists.debian.org/debian-devel/2017/11/msg00153.html https://wiki.debian.org/AppArmor/Contribute/Upstream#Debian_.2F_Upstream_relationship

Helpfile says tag=<integer> (1 - 4094) VLAN tag to apply to packets on this interface. I'm reading this as "tagged outside the guest and untagged inside." Is this a correct interpretation?

Left out the OVSPort: iface eth0 inet manual ovs_bridge vmbr0 ovs_type OVSPort Now the untagged guests are working as expected, but the KVM guest I put into VLAN 88 can not ping the router. Network device is set bridge=vmbr0 tag=88, but the guest OS is not configured for tagging.

I've used OVS in PVE with VLANs previously, but the tagging was done by the guests. I'm trying to convert an existing node form linuxbridge to OVS and seem to have missed something basic. /etc/network/interfaces file looks like this: #auto lo iface lo inet loopback auto vmbr0 allow-ovs vmbr0...

Stopped the VM, fixed memory at 2.5 gbytes, restarted. No change. Click + enter does not change anything. ALT + F1 (from the keyboard) got me a login prompt. Thanks!

Here are both of them: root@pve1:~# qm config 102 balloon: 768 bootdisk: scsi0 cores: 3 ide2: local:iso/Ubuntu-16.04.mini.iso,media=cdrom memory: 2560 name: unms net0: virtio=7A:76:F3:9F:6C:CB,bridge=vmbr0 numa: 0 onboot: 1 ostype: l26 scsi0: zfs-local:vm-102-disk-1,size=64G scsihw...

NoVNC consoles work just fine in all of our LXC's. Recently set up two KVM guests, neither of which will give us a console. Grey 'connected' banner comes up and then goes away, leaving just a black screen. No cursor, no change from keyboard or mouse inputs:

Yes, it will work unconfined -- but that kind of defeats the purpose of running LXCs. I am still curious about the roadmap for LXC updates.

I have a report of Docker installing successfully and running well in an LXC (Ubuntu 16.04 container on Ubuntu 17.04 host with LXC version 2.17). Is there a roadmap for this LXC update in PVE? thank you~

I inquired about this some time ago (on the previous forum platform) and was told that this could be done by an admin. Lost track of it for some long time, and on the new platform I am unable to start a conversation with a staff member (at least with the four that I tried). thank you~

Thank you~

Command-line works. Thanks! Left out that I still don't see where to do this in the GUI. I can rename a KVM in the Options area, but the Name field does not appear there for LXC's.

I'm guessing I missed something obvious here, but how does one rename an LXC on PVE 4.4?

Just wanted to circle back that boot2docker.iso (downloaded from https://github.com/boot2docker/boot2docker/releases/latest) runs just fine in a KVM, and is very lightweight.

Thanks, Bill. I've been following the Docker discussions here for some time and understand the lack of a fit between SAAS and Proxmox. I just really prefer containers. I downloaded boot2docker.iso from the release page and booted it in a KVM. Installer script depends on bash, which is not...

Very low powered nodes here, so I was hoping to avoid KVM. Had not heard of boot2docker. Downloads on boot2docker.io are for Windows and OS X. Building an ISO apparently depends on Docker. https://github.com/dhiltgen/docker-machine-kvm perhaps? +1 for Docker support under Proxmox, or at...

We have a couple of apps we need to deploy which are being provided as Docker images (no other options currently available from the developers. We would prefer (strongly) to run them in LXC on Proxmox. http://stackoverflow.com/questions/22085657/can-docker-run-inside-a-linux-container has some...

Took some time re-learning the (not quite standard) Cisco SG300 command line syntax for me to figure out that a clueless maintenance guy had moved the server NIC cable from ge3 to ge5. Added vlan11 to that and everything is back online.