Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #256283
| From | Greg Wooledge <greg@wooledge.org> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: what's the right way to resolve localhost's IPs |
| Date | 2023-03-23 00:40 +0100 |
| Message-ID | <GcgdH-eoEk-1@gated-at.bofh.it> (permalink) |
| References | <GbViV-ebLW-5@gated-at.bofh.it> <GbW5j-ech4-1@gated-at.bofh.it> <Gce2d-enkx-7@gated-at.bofh.it> <Gcevg-env1-5@gated-at.bofh.it> <GcfKG-eoue-45@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Thu, Mar 23, 2023 at 07:06:55AM +0800, Jeremy Ardley wrote: > I am the guilty party who had docker. I have not raised any issue about it. The instance is not used any more and was an experiment in running nextcloud on an arm server Then perhaps you can enlighten me: why does anyone (Docker user or otherwise) need to write a shell script to list the IPv4 addresses of the local system's network interfaces? I can't think of any reasons other than "I want to update dynamic DNS" (for which a dhclient hook is better suited, with the new IP address being supplied in the environment), or "I need to use it to set up firewall rules", a topic with which I'll admit I'm not very experienced, but which doesn't seem particularly important on exposed servers. I would think you'd simply shut down all the services you don't want running, rather than leaving them in place but trying to block them with a firewall.
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
what's the right way to resolve localhost's IPs fh@dnsbed.com - 2023-03-22 02:20 +0100
Re: what's the right way to resolve localhost's IPs Jeremy Ardley <jeremy@ardley.org> - 2023-03-22 03:10 +0100
Re: what's the right way to resolve localhost's IPs fh@dnsbed.com - 2023-03-22 03:40 +0100
Re: what's the right way to resolve localhost's IPs Gregory Seidman <gsslist+debian@anthropohedron.net> - 2023-03-22 21:40 +0100
Re: what's the right way to resolve localhost's IPs Tom Furie <tom@furie.org.uk> - 2023-03-22 22:20 +0100
Re: what's the right way to resolve localhost's IPs Greg Wooledge <greg@wooledge.org> - 2023-03-22 22:50 +0100
Re: what's the right way to resolve localhost's IPs Jeremy Ardley <jeremy@ardley.org> - 2023-03-23 00:10 +0100
Re: what's the right way to resolve localhost's IPs Greg Wooledge <greg@wooledge.org> - 2023-03-23 00:40 +0100
Re: what's the right way to resolve localhost's IPs Jeremy Ardley <jeremy@ardley.org> - 2023-03-23 01:00 +0100
Re: what's the right way to resolve localhost's IPs Nicolas George <george@nsup.org> - 2023-03-23 08:50 +0100
Re: what's the right way to resolve localhost's IPs Jeremy Ardley <jeremy@ardley.org> - 2023-03-23 09:00 +0100
Re: what's the right way to resolve localhost's IPs Lee <ler762@gmail.com> - 2023-03-23 12:00 +0100
Re: what's the right way to resolve localhost's IPs Emanuel Berg <incal@dataswamp.org> - 2023-03-30 07:50 +0200
Re: what's the right way to resolve localhost's IPs fh@dnsbed.com - 2023-03-30 10:10 +0200
csiph-web