[PVE-User] Fedora 28

Discussion:

lord_Niedzwiedz

2018-09-05 13:48:40 UTC

Permalink

Container not set static ip withou this file ;-/

I must add:

vi /etc/sysconfig/network

Stoiko Ivanov

2018-09-05 15:25:16 UTC

Permalink

Hi,

where did you get the container image from?

(Currently we do not yet have an official Fedora 28 template)
The ones from http://uk.images.linuxcontainers.org/images/ do work with
a static ip set.

Recently we changed the network setup for Fedora >= 27, to create
systemd-networkd files, since this is what is used in the upstream
templates.

Maybe just install systemd-networkd?

Regards,
stoiko

On Wed, 5 Sep 2018 15:48:40 +0200

Post by lord_Niedzwiedz
Container not set static ip withou this file ;-/
vi /etc/sysconfig/network
_______________________________________________
pve-user mailing list
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

lord_Niedzwiedz

2018-09-06 08:33:33 UTC

Permalink

Hi,
I get yours offical Fedora 27.
And this didint work properly.

After added file /etc/sysconfig/network I upgrade distribution.
Works fine ;)

Regards,
Gregory

Post by Stoiko Ivanov
Hi,
where did you get the container image from?
(Currently we do not yet have an official Fedora 28 template)
The ones from http://uk.images.linuxcontainers.org/images/ do work with
a static ip set.
Recently we changed the network setup for Fedora >= 27, to create
systemd-networkd files, since this is what is used in the upstream
templates.
Maybe just install systemd-networkd?
Regards,
stoiko
On Wed, 5 Sep 2018 15:48:40 +0200

Thomas Lamprecht

2018-09-07 11:44:48 UTC

Permalink

Post by lord_Niedzwiedz
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

Stoiko Ivanov

2018-09-11 13:00:27 UTC

Permalink

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!

Post by Thomas Lamprecht

Post by lord_Niedzwiedz
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,
# pveam download STORAGE fedora-28-default_20180907_amd64.tar.xz
cheers,
Thomas

Problem is in configuration fedora system inside (fedora-28 too).
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

lord_Niedzwiedz

2018-09-11 13:08:35 UTC

Permalink

Hi,

I did not change anything except the two things below.
And fedora works with network after restart.

***@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.
[***@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

Post by Stoiko Ivanov
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!

Post by Thomas Lamprecht

Post by lord_Niedzwiedz
Hi,
I get yours offical Fedora 27.

Stoiko Ivanov

2018-09-11 14:31:51 UTC

Permalink

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!

Post by lord_Niedzwiedz
Hi,
I did not change anything except the two things below.
And fedora works with network after restart.
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.
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

Post by Stoiko Ivanov
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!

Post by Thomas Lamprecht

Post by lord_Niedzwiedz
Hi,
I get yours offical Fedora 27.

lord_Niedzwiedz

2018-09-12 06:31:11 UTC

Permalink

***@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

Post by Stoiko Ivanov
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!

Post by Stoiko Ivanov
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!

Post by Thomas Lamprecht

Post by lord_Niedzwiedz
Hi,
I get yours offical Fedora 27.

Stoiko Ivanov

2018-09-12 07:27:48 UTC

Permalink

Hi,

The problem with Fedora containers was fixed with pve-container 2.0-25.
Could you try again after upgrading?

Cheers,
stoiko

Post by lord_Niedzwiedz
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

Post by Stoiko Ivanov
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!

Post by Thomas Lamprecht

Post by lord_Niedzwiedz
Hi,
I get yours offical Fedora 27.

lord_Niedzwiedz

2018-09-12 09:01:25 UTC

Permalink

How i make this upgrading ??!!

***@hayne1:~# apt upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
***@hayne1:~# apt update
Ign:1 http://ftp.pl.debian.org/debian stretch InRelease
Hit:2 http://ftp.pl.debian.org/debian stretch-updates InRelease
Hit:3 http://ftp.pl.debian.org/debian stretch Release
Hit:4 http://security.debian.org stretch/updates InRelease
Ign:6 https://enterprise.proxmox.com/debian/pve stretch InRelease
Err:7 https://enterprise.proxmox.com/debian/pve stretch Release
401 Unauthorized
Reading package lists... Done
E: The repository 'https://enterprise.proxmox.com/debian/pve stretch
Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is
therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user
configuration details.

Post by Stoiko Ivanov
Hi,
The problem with Fedora containers was fixed with pve-container 2.0-25.
Could you try again after upgrading?
Cheers,
stoiko

Post by Stoiko Ivanov
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!

Post by Thomas Lamprecht

Post by lord_Niedzwiedz
Hi,
I get yours offical Fedora 27.

Mark Adams

2018-09-12 09:08:01 UTC

Permalink

If you don't have a license, you need to change the repository.

https://pve.proxmox.com/wiki/Package_Repositories#_proxmox_ve_no_subscription_repository

How i make this upgrading ??!!
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Ign:1 http://ftp.pl.debian.org/debian stretch InRelease
Hit:2 http://ftp.pl.debian.org/debian stretch-updates InRelease
Hit:3 http://ftp.pl.debian.org/debian stretch Release
Hit:4 http://security.debian.org stretch/updates InRelease
Ign:6 https://enterprise.proxmox.com/debian/pve stretch InRelease
Err:7 https://enterprise.proxmox.com/debian/pve stretch Release
401 Unauthorized
Reading package lists... Done
E: The repository 'https://enterprise.proxmox.com/debian/pve stretch
Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is
therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user
configuration details.
Hi,

Post by Stoiko Ivanov
The problem with Fedora containers was fixed with pve-container 2.0-25.
Could you try again after upgrading?
Cheers,
stoiko

Post by lord_Niedzwiedz
Hi,
I did not change anything except the two things below.
And fedora works with network after restart.
arch: amd64
cores: 2
hostname: wanwww14
memory: 8192
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.
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,

Post by Stoiko Ivanov
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!

Hi,

Post by Thomas Lamprecht

Post by lord_Niedzwiedz
I get yours offical Fedora 27.