Re: LXC container update fail

2020-06-15 Thread Gokan Atmaca
> Try updating and/or installing libgnutls30 and ca-certificates from packages installed. On Mon, Jun 15, 2020 at 9:58 AM Andrei POPESCU wrote: > > On Du, 14 iun 20, 11:15:55, Gokan Atmaca wrote: > > > Does internet access work properly from the container? > > yes. domain name resolution, Ping

Re: LXC container update fail

2020-06-14 Thread Andrei POPESCU
On Du, 14 iun 20, 11:15:55, Gokan Atmaca wrote: > > Does internet access work properly from the container? > yes. domain name resolution, Ping etc. It works. > > root@nginx2:~# ping -c 2 google.com > PING google.com (172.217.18.14) 56(84) bytes of data. > 64 bytes from fra15s28-in-f14.1e100.net

Re: LXC container update fail

2020-06-14 Thread Jim Popovitch
On Sun, 2020-06-14 at 22:40 +0300, Gokan Atmaca wrote: > > Are you able to ping 151.101.12.204 or deb.debian.org from the same lxc? > yes; > > root@nginx2:~# ping deb.debian.org > PING debian.map.fastly.net (151.101.14.133) 56(84) bytes of data. > 64 bytes from 151.101.14.133 (151.101.14.133): icm

Re: LXC container update fail

2020-06-14 Thread Gokan Atmaca
> Are you able to ping 151.101.12.204 or deb.debian.org from the same lxc? yes; root@nginx2:~# ping deb.debian.org PING debian.map.fastly.net (151.101.14.133) 56(84) bytes of data. 64 bytes from 151.101.14.133 (151.101.14.133): icmp_seq=1 ttl=58 time=5.21 ms 64 bytes from 151.101.14.133 (151.101.1

Re: LXC container update fail

2020-06-14 Thread Jim Popovitch
On Sun, 2020-06-14 at 11:15 +0300, Gokan Atmaca wrote: > > Does internet access work properly from the container? > yes. domain name resolution, Ping etc. It works. > > root@nginx2:~# ping -c 2 google.com > PING google.com (172.217.18.14) 56(84) bytes of data. > 64 bytes from fra15s28-in-f14.1e

Re: LXC container update fail

2020-06-14 Thread Gokan Atmaca
> Does internet access work properly from the container? yes. domain name resolution, Ping etc. It works. root@nginx2:~# ping -c 2 google.com PING google.com (172.217.18.14) 56(84) bytes of data. 64 bytes from fra15s28-in-f14.1e100.net (172.217.18.14): icmp_seq=1 ttl=118 time=5.28 ms 64 bytes f

Re: LXC container update fail

2020-06-14 Thread Andrei POPESCU
On Du, 14 iun 20, 10:33:52, Gokan Atmaca wrote: > > Mirror is out of date. Wait an hour and try again. > > It's been a week ago. Ubuntu container with Lxc fails. > Debian,ubuntu they all have the same mistake. Does internet access work properly from the container? Kind regards, Andrei -- http:/

Re: LXC container update fail

2020-06-14 Thread Gokan Atmaca
> Mirror is out of date. Wait an hour and try again. It's been a week ago. Ubuntu container with Lxc fails. Debian,ubuntu they all have the same mistake. On Sat, Jun 13, 2020 at 5:29 PM Sven Hartge wrote: > > Gokan Atmaca wrote: > > > Container is not updating. Why could it be ? > > > ---> Er

Re: LXC container update fail

2020-06-13 Thread Sven Hartge
Gokan Atmaca wrote: > Container is not updating. Why could it be ? > ---> Error is as follows: > root@debWeb0:~# apt update > Ign:1 http://deb.debian.org/debian buster InRelease > Ign:2 http://security.debian.org/debian-security buster/updates InRelease > Err:3 http://security.debian.org/debian

LXC container update fail

2020-06-13 Thread Gokan Atmaca
Hello Container is not updating. Why could it be ? ---> Error is as follows: root@debWeb0:~# apt update Ign:1 http://deb.debian.org/debian buster InRelease Ign:2 http://security.debian.org/debian-security buster/updates InRelease Err:3 http://security.debian.org/debian-security buster/updates Re