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
