The host’s local dns resolution is not configured. The problem of the host’s hosts being unable to be resolved in docker has been solved. Surprisingly
Edit the /etc/resovel.conf file
One immediate issue I can think of here is that editing resolv.conf directly is no longer supported and not recommended (because the changes do not survive a reboot) - unless you install the resolvconf package?
We got this working. I’m not sure if it was on my buddys end.
Here the steps:
Add new sub in ntfy app with the private ID and using another server (ntfy.mydomain.com)
In settings also use the ntfy url as default Server
add the upstream-base-url: “https://ntfy.sh” property in server.yaml and restart ntfy
We love laws, and would pay if we want to watch movies.
I think you’ve hit the nail on the head here - particularly around the point re: privacy. I expect that other people are willing to abide by the laws also, but it’s very easy to see how rising prices will simply fuel the pirate industry even further. Nobody likes to be “ripped off” or “held to ransom”, and there are always going to be those who would rather not pay at all and put up with a poor video image taken in the cinema with someone’s head bobbing up and down, or overhearing someone complain they asked for an ice cream but got a donut… 🙂
The rising costs of viewing material is what is in essence the fuel for the piracy market - not just viewing either - it used to be the case (before digital downloads of music tracks) that people were pirating CD’s because of the cost. With the onset of online music stores, that’s probably a thing of the past - I can’t recall overhearing anyone saying they spend all of their free time searching for mp3’s etc recently, unless I’m out of touch, but the film industry is encouraging piracy with the spiralling costs of attending the cinema etc - not to mention being robbed in broad daylight if you want refreshments.