Re: LXC container update fail
> 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.14.133): icmp_seq=2 ttl=58 time=5.41 ms
On Sun, Jun 14, 2020 at 5:31 PM Jim Popovitch <jim@k4vqc.com> wrote:
>
> 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.1e100.net (172.217.18.14): icmp_seq=1
> > ttl=118 time=5.28 ms
> > 64 bytes from fra15s28-in-f14.1e100.net (172.217.18.14): icmp_seq=2
> > ttl=118 time=5.38 ms
> >
>
> Are you able to ping 151.101.12.204 or deb.debian.org from the same lxc?
>
>
>
> -Jim P.
>
Reply to: