AI-ambivalent bricoleur.
FOSS/LL, GNU/Linux, Python, Rust, Javascript, biking/pratique du vélo.
| Pronouns | he/him |
| Languages | eng/fr |
@chris in my experience this is usually not necessary since most firewalls will allow outbound connections by default.
I did have this issue once in a VPS and it turned out to be a MTU blackholing issue.
You try doing `docker exec -ti <container_name> sh` to get access to a shell inside the container. Then you can typically use wget, curl or ping to test if the internet is reachable from inside the container network namespace.
@chris I'd start with `docker logs <container_name> if you haven't done that yet. However, if it's a firewall issue or some other issue with the network bridge, this won't give you anything useful.
Have you confirmed that nginx is listening on the specified port inside the container?
Linked on Lemmy: https://www.stilldrinking.org/stop-talking-to-technology-executives-like-they-have-anything-to-say
"I can’t think of a better argument for a humanities requirement than a billionaire being asked “how do we know what is real?” and responding with “cryptographic signatures.”
There should be a genre of music called burnoutcore for music that could have appeared in 2004s Burnout 3.
Soundtrack for that game is like a time machine.
Suggested inclusion: Bowling for soup
#til about docker contexts.
Turns out docker already has facilities for securely running commands on a remote host via tcp socket.
Wonder how this fits in with platforms like komodo or portainer that have their own core + agent model for managing remote servers 🤔
Turns out was something weird going on with DNS resolution via router. Dig shows consistent errors related to malformed message packets.
Updating nameserver to 9.9.9.9 in resolveconf fixed the issue.
Recently switched from arch to #nixos and encountering a strange networking issue where network over wifi drops out every ~30 seconds or so. Very occasionally had problems on arch but nothing this bad.
Have been enjoying getting to grips with #networking but this one is particular annoying.
I stared at tcpdump for awhile but couldn't make much sense of output.
NIC is an Intel Killer AX1650w. Delightful wifi setup in my rental is behind an extender.
Anything obvious I can check?
TIA
