• 0 Posts
  • 36 Comments
Joined 10 months ago
cake
Cake day: August 27th, 2023

help-circle
  • shasta@lemm.eetoScience Memes@mander.xyzEvidence
    ·
    3 days ago

    That's what I was thinking. And I just noticed that in 2 of the pics the shoulder strap to her shirt is different. If it's not different women, it's at least different shirts in some of the panels












  • shasta@lemm.eetoFuck Cars@lemmy.mlYes, also Teslas
    ·
    edit-2
    8 months ago

    EVs also help with the brake disc "dust" since a lot of the braking is "regenerative breaking" done by the electric motor and does not use the brake pads at all. They require less maintenance, and have fewer parts in them, so fewer manufacturing materials. With very few exceptions, they are also smaller vehicles with more safety features which should result in fewer pedestrian casualties.

    Obviously having no vehicles at all would be even better at solving these issues, but that's not practical for our current reality. Maybe in 100 years.

    I will say that "autopilot" features should absolutely be outlawed and cause nothing but trouble to everyone.





  • Yes that's correct. And containers are not really portable in the way you described. They do have a mini OS in them but the state is not saved when they are "offline". So you can think of it as more of a template, called an image. You can save the image to a file, and move that to a new pc and load that back into Docker, but that's usually unnecessary. As long as you have Internet, you just need to know the name of the image and Docker will just download it if it doesn't already have it. For most popular programs, you'll find an image for it already created so just follow the instructions on what settings to use for things like volume mounts and environment variables. This configuration of variables can be saved into a Docker Compose file for easy reuse instead of typing really long command line to run your container. This Compose file is all you really need to move to the other PC and it'll just download your image and run everything as before.



  • The data that your software interacts with is external to a container but can be mapped to the container file system so that the software can interact with it. For example, your Minecraft server relies on disk files consisting of the world state and server config files (and plugins if you have any). These will still be on your host system, not inside the container. In order to transfer this to another system, you have to take those files from your host and move them to the new host. Then copy your docker config files over too so you can start a new container that points to your files on disk and it should function the same as it did before, but possibly with a different IP address.

    An easy way to think of it is that a container can be restarted, like maybe when you restart the PC. When a container is restarted, all the files in the container reset to their initial state. If you go into a container and create files then restart the container, those files will be gone. Any data that needs to be persisted between restarts needs to go on your host filesystem and volume mount it to the container.