Search results

Though this is already old, can't find a thread on it here. https://tech.vijayp.ca/linux-kernel-bug-delivers-corrupt-tcp-ip-data-to-mesos-kubernetes-docker-containers-4986f88f7a19

(ie, he cant. which is a reduction in features from a VZ container where df showed the proper limit.)

How can the CT admin inside the container see his limit readily?

Sure - outside the container, but this is inside -- will the container be limited at 12GB? And even if it is, why can't the users of the container see that they're limited to 12GB in the df, like with openVZ containers in 3.4?

according to this https://forum.proxmox.com/threads/convert-physical-machine-to-lxc.23924/ you cant.

so many changes moving to proxmox 4.x wow. (Ive got some legacy Centos 4.8 and 5 here that cant easily be upgraded). Guess it's back to 3.4...

Finally figured out how to create a container on pve 4.1. (I had installed PVE4.1 on a ZFS mirror, not sure if that has anything to do with it, but I had to go and create myself another datastore, which I did as ZFS). The datastore is CTDATA: enabled, active, content = disk image,container...

My node is already online (I think, I mean, what does 'online' mean? the server is powered up and I can hit webconsole on https:8006..) - why is a reboot necessary?

When pinning many proxmox consoles in firefox or chrome, the favicon is all thats shown for the browser tab. Hard to differentiate different machines consoles til you actually load the tab fully. For unloaded/dormant tabs this becomes a heavyweight procedure to go through 4-5 tabs+ to find what...

Re: firewall not working on vm with firewall=1 on nic and fw on in firewall -> option uh turning on the firewall blocks :8006 webconsole?

Re: firewall not working on vm with firewall=1 on nic and fw on in firewall -> option Thanks!! Wow that's buried. Didnt think to look there. Esp when you hit the Firewall tab and it shows an empty list, and the tabs are at bottom (not anywhere near the top where Im clicking on my giant monitor...

Set "firewall on" on in the vm Firewall -> Options tab, and in Hardware -> NIC, and restarted VM. no go. dont see any rules in iptables -L or iptables-save. I do see rules in /etc/pve/firewall/100.fw. Pve-firewall stop && start doesnt work however. running pve-manager/3.4-6/102d4547 (running...

I can create containers. I had installed proxmox from the installation GUI with ZFS RAID 1 on two disks, I didnt do anything post install to the disk layout. Just didnt realise I had to manually create a ZFS pool for containers.

yep doing that now. creating... done. lack of sleep and not understanding the new disk system got me into this corner. gentle suggestion of some kind of reminder that 'containers cant be created on default local storage if zfs was used for installation' might be good in the GUI. thanks again...

root@tesla:~# pveversion pve-manager/4.0-48/0d8559d0 (running kernel: 4.2.2-1-pve) Im following this thread after I tried to create a container and got exactly the same as this thread: https://forum.proxmox.com/threads/23884-Can-t-create-LXC-container-on-ZFS-local which led me to here...

thanks for your patience. here's the original post of my storage.cfg dir: local path /var/lib/vz content images,iso,rootdir,vztmpl maxfiles 0 zfspool: data1 pool rpool content rootdir,images I added and removed containers, which seems to toggle...

ok fixed. sorry. bad day here.anyway trying to repost contents of the file.

<forum formatting issue details elided>

<forum formatting issue details elided>

note this is all a stock install right out of the box, these are the first actions i've taken since install:- create CT as per normal under 3.4 etc - watch it fail- find out i need to create ZFS storage for it, try to install, cant choose anything but local, reboot- try again with all combos...