Hi, The problem with Fedora containers was fixed with pve-container 2.0-25. Could you try again after upgrading?
Cheers, stoiko On Wed, Sep 12, 2018 at 08:31:11AM +0200, lord_Niedzwiedz wrote: > root@hayne:~# pveversion -v > proxmox-ve: 5.2-2 (running kernel: 4.15.17-1-pve) > pve-manager: 5.2-1 (running version: 5.2-1/0fcd7879) > pve-kernel-4.15: 5.2-1 > pve-kernel-4.15.17-1-pve: 4.15.17-9 > corosync: 2.4.2-pve5 > criu: 2.11.1-1~bpo90 > glusterfs-client: 3.8.8-1 > ksm-control-daemon: 1.2-2 > libjs-extjs: 6.0.1-2 > libpve-access-control: 5.0-8 > libpve-apiclient-perl: 2.0-4 > libpve-common-perl: 5.0-31 > libpve-guest-common-perl: 2.0-16 > libpve-http-server-perl: 2.0-8 > libpve-storage-perl: 5.0-23 > libqb0: 1.0.1-1 > lvm2: 2.02.168-pve6 > lxc-pve: 3.0.0-3 > lxcfs: 3.0.0-1 > novnc-pve: 0.6-4 > proxmox-widget-toolkit: 1.0-18 > pve-cluster: 5.0-27 > pve-container: 2.0-23 > pve-docs: 5.2-3 > pve-firewall: 3.0-8 > pve-firmware: 2.0-4 > pve-ha-manager: 2.0-5 > pve-i18n: 1.0-5 > pve-libspice-server1: 0.12.8-3 > pve-qemu-kvm: 2.11.1-5 > pve-xtermjs: 1.0-5 > qemu-server: 5.0-26 > smartmontools: 6.5+svn4324-1 > spiceterm: 3.0-5 > vncterm: 1.5-3 > zfsutils-linux: 0.7.8-pve1~bpo9 > > W dniu 11.09.2018 o 16:31, Stoiko Ivanov pisze: > > Hi, > > > > cannot reproduce the problem with a similar config (mac and ip addresses > > changed, but else the same). > > > > which versions of our stack do you run? (please post the output of > > pveversion -v). > > > > Thanks! > > > > > > On Tue, Sep 11, 2018 at 03:08:35PM +0200, lord_Niedzwiedz wrote: > > > Hi, > > > > > > I did not change anything except the two things below. > > > And fedora works with network after restart. > > > > > > root@hayne1:/rpool# pct config 102 > > > arch: amd64 > > > cores: 2 > > > hostname: wanwww14 > > > memory: 8192 > > > net0: > > > name=eth0,bridge=vmbr0,firewall=1,gw=8.8.152.1,hwaddr=F5:E4:9B:64:22:84,ip=8.8.152.104/24,type=veth > > > ostype: fedora > > > rootfs: local-zfs:subvol-102-disk-1,size=28G > > > swap: 1024 > > > unprivileged: 1 > > > > > > I don't change antyhing. > > > This is config from Proxmox GUI inside Fedora. > > > [root@wanwww8 ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth0 > > > DEVICE=eth0 > > > ONBOOT=yes > > > BOOTPROTO=none > > > IPADDR=8.8.152.104 > > > NETMASK=255.255.255.0 > > > GATEWAY=8.8.152.1 > > > > > > Only these two changes below are required for the Fedora to start up with > > > a > > > working network. > > > Of course, the native server should also have properly configured dns, > > > etc. > > > > > > Gregory Bear > > > > > > > Hi, > > > > > > > > could you please send the container-config (`pct config $vmid`) from the > > > > node and the contents of all files (redact if needed) from > > > > /etc/systemd/network/* ? > > > > > > > > Thanks! > > > > > > > > On Tue, Sep 11, 2018 at 02:38:59PM +0200, lord_Niedzwiedz wrote: > > > > > > > Hi, > > > > > > > I get yours offical Fedora 27. > > > > > > you should now be able to get the Fedora 28 template directly from > > > > > > us. > > > > > > # pveam update > > > > > > > > > > > > should pull the newest appliance index (gets normally done > > > > > > automatically, > > > > > > once a day) then either download it through the WebUI or with CLI: > > > > > > > > > > > > # pveam download STORAGE fedora-28-default_20180907_amd64.tar.xz > > > > > > > > > > > > cheers, > > > > > > Thomas > > > > > Problem is in configuration fedora system inside (fedora-28 too). > > > > > > > > > > I must add this two things: > > > > > > > > > > chkconfig --levels 2345 network on > > > > > > > > > > vi /etc/sysconfig/network > > > > > NETWORKING=yes > > > > > HOSTNAME=ala_ma_kota > > > > > GATEWAY=88.44.152.1 > > > > > > > > > > Now i restart contener and ip from Proxmox works. > > > > > > > > > > ip a > > > > > > > > > > Cheers, > > > > > Gregory Bear > > > > > > > > > > > _______________________________________________ pve-user mailing list [email protected] https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
