• 78 Posts
  • 866 Comments
Joined 1 year ago
cake
Cake day: July 2nd, 2023

help-circle


    1. For all the mentioned cases, if your firewall blocks incoming packets by default, no one can access it, no matter what is the source of the port being open.

    2. You don’t configure it on the docker level, at least if you care about outside connections. If you mean from your local computer to a docker container, by default you cannot connect, unless you expose the port to the system. If you mean from other docker containers, just create your own separate network to run the container in and even docker containers cannot access the ports.

    3. I usually use netstat -tulpn, it lists all ports, not only docker, but docker is included. docker ps should also show all exposed ports and their mappings.

    In general, all docker containers run on some internal docker network. Either the default or a custom one. The network’s ports don’t interfere with your own, that’s why you can have 20 nginx servers running in a docker container on the same port. When you bind a port in docker, you basically create a bridge from the docker network to your PC’s local network. So now anything that can connect to your PC can also connect to the service. And if you allow connection to the port from outside the network, it will work as well. Note that port forwarding on your router must be set up.

    So in conclusion, to actually make a service running in docker visible to the public internet, you need to do quite a few steps!

    • bind a port to your local host
    • have your local firewall allow connection to the port
    • have your router set up to forward connections on the port to your machine

    On Linux, local firewall is usually disabled by default, but the other two steps require you to actively change the default config. And you mention that all incoming traffic is dropped using UFW, so all three parts should be covered.













  • Settings, mostly. The layering is always there, but how visible it is depends on the layer height. Both the Depresso and Spyro were made with 0.2mm layer height, which is a good compromise between looks-good/prints-fast. If you want something that looks really nice, you’d go to 0.08mm layer height (the lowest this particular printer can go with this particular nozzle size). The print would take around 2.5 times longer with 0.08mm layer height.

    Material also affects this, but PLA generally is the easiest to print with and looks among the best visually. If the print speed were really high it would affect it as well, but it was well under the maximum speeds.

    This is a FDM printer which basically lays one layer of heated plastic over another, there are also SLA printers which can go much lower layer heights and thus the prints are visually much better, though use-case of such printers are limited to pretty looking pieces, you can’t really make anything functional with them.

    Edit: If you want the prints to look really great, you’re gonna have to do some post-processing anyway, like sanding down the uglier parts and painting it with some acrylic paint. That way you avoid the visible layers as well.


  • Bambu Lab A1 and mostly PLA for material (aka the easiest one to print).

    When I need something flexible, I use some TPU. And when I need something that will hold for a long time, I use PETG.

    I make all kinds of stuff, mostly toys and household items, sometimes I design something myself (generally the stuff that’s meant to be useful, not pretty), sometimes I use models other people created.

    Currently I’m printing a puzzle for kids.

    Edit: a recent print of mine:

    3D printed Spyro the Dragon