I installed a few different distros, landed on Cinnamon Mint. I’m not a tech dummy, but I feel I’m in over my head.

I installed Docker in the terminal (two things I’m not familiar with) but I can’t find it anywhere. Googled some stuff, tried to run stuff, and… I dunno.

I’m TRYING to learn docker so I can set up audiobookshelf and Sonarr with Sabnzbd.

Once it’s installed in the terminal, how the hell do I find docker so I can start playing with it?

Is there a Linux for people who are deeply entrenched in how Windows works? I’m not above googling command lines that I can copy and paste but I’ve spent HOURS trying to figure this out and have gotten no where…

Thanks! Sorry if this is the wrong place for this

EDIT : holy moly. I posted this and went to bed. Didn’t quite realize the hornets nest I was going to kick. THANK YOU to everyone who has and is about to comment. It tells you how much traction I usually get because I usually answer every response on lemmy and the former. For this one I don’t think I’ll be able to do it.

I’ve got a few little ones so time to sit and work on this is tough (thus 5h last night after they were in bed) but I’m going to start picking at all your suggestions (and anyone else who contributes as well)

Thank you so much everyone! I think windows has taught me to be very visually reliant and yelling into the abyss that is the terminal is a whole different beast - but I’m willing to give it a go!

  • onlinepersona@programming.devEnglish
    291·
    8 months ago

    Docker is one of the container technologies

    Containers vs Images

    This is a very simplified explanation, which hopefully clears up for you. As with all simplifications, they aren’t entirely correct.

    Containers put processes, files, and networking into a space where they are secluded from the rest. You main OS is called the host and the container is called the guest. You can selectively share resources with the guest. To use an analogy, if you house were the computer with linux, if you took a room, put tools and resources for those tools into it, put workers into it, got them to start working and locked the door, they’d be contained in the room, unable to break out. If you want to give workers access to resources, you either a window, a corridor, or even a door depending on much access you want to give them.

    Containers are created from an image. Think of it as the tools, resources, and configuration required every time you create a room in your house for workers to do a job. The woodworkers will need different tools and resources than say metalworkers.

    Most images are stored on DockerHub. So when you do docker pull linuxserver/sonarr you download the image. When you do docker run linuxserver/sonarr you create a container from an image.

    Installation

    You’re on Cinnamon Mint which is linux distribution derived from another linux distribution called debian. You have to follow the installation instructions. Everything is there. If something doesn’t work, it’s most likely because you skipped a step. The most important ones are the post-installation steps:

    • Adding your user to the docker group
    • Logging out and back in (or simply restarting)

    Those are the most commonly missed steps. I’ve fallen for this trap too!

    Local help

    To use linux, you need to learn about ways to help yourself or find help. On linux, most well-written programs print a help. Simply running the command without any arguments most often output a help text --> running docker does so. If they don’t, then the --help flag often does --> docker --help. The shorthand is -h --> docker -h.

    Some commands have sub commands e.g docker run, docker image, docker ps, … . Those subcommands also take flags of which -h and --help are available.

    The help output is often not extensive and programs often have a manual. To access it the command is man --> man find will output the manual for the find command. Docker doesn’t have a local manual but an online one.

    For clarification when running a command there are different ways to interpret the text after the command:

    Flags/Options

    These are named parameters to the command. Some do not take input like -h and --help which are called flags. Some do like --file /etc/passwd and are often called options.

    Arguments

    These are unnamed parameters and each command interprets them differently. echo "hello world" --> echo is the command and "hello world" is the argument. Some commands can take multiple arguments

    Running containers

    Imperatively

    As described above docker run linuxserver/sonarr runs an image in a container. However, it runs in the foreground (as opposed to the background in what is most often called a “daemon”). Starting in the foreground is most likely not how you want to run things as that means if you close your terminal, you end the process too. To run something in the background, you use docker run --detatch linuxserver/sonarr.

    You can pass options like -v or --volume to make a file or folder from your host system available in the guest e.g -v /path/on/host:/tmp/path/in/guest. Or -p / --port to forward a host port to a guest port e.g -p 8080:80. That means if you access port 8080 on your host, the traffic will be forwarded to port 80 in the guest.

    These are imperatives as in you command the computer to do a specific action. Run that docker image, stop that docker container, restart these containers, start a container with this port forward and that volume with this user …

    Declaratively

    If you don’t want to keep typing the same commands, you can declare everything about your containers up front. Their volumes, ports, environment variables, which image is used, which network card/interface they have access to, which other network they share with other containers, and so on.

    This is done with docker-compose or docker compose for newer docker versions (not all operating systems have the new docker version).

    This already a long text, so if you want to know more, the best resource is the docker compose manual and the compose file reference.

    Hopefully this helped with the basics and understanding what you’re doing. There are probably great video resources out there that explain it more didactically than I do with steps you can follow along.

    Good luck!

    CC BY-NC-SA 4.0

    • Arthur Besse@lemmy.mlMEnglish
      2·
      8 months ago

      You main OS is called the host and the container is called the guest

      The word “guest” is generally used for virtual machines, not containers.

        • Arthur Besse@lemmy.mlMEnglish
          1·
          8 months ago

          Can containers boot on their own? Then they are hosts, if not they are guests.

          It depends what you mean by “boot”. Linux containers are by definition not running their own kernel, so Linux is never booting. They typically (though not always) have their own namespace for process IDs (among other things) and in some cases process ID 1 inside the container is actually another systemd (or another init system).

          However, more often PID 1 is actually just the application being run in the container. In either case, people do sometimes refer to starting a container as “booting” it; I think this makes the most sense when PID 1 in the container is systemd as the word “boot” has more relevance in that scenario. However, even in that case, nobody (or at least almost nobody I’ve ever seen) calls containers “guests”.

          As to calling containers “hosts”, I’d say it depends on if the container is in its own network namespace. For example, if you run podman run --rm -it --network host debian:bookworm bash you will have a container that is in the same network namespace as your host system, and it will thus have the same hostname. But if you omit --network host from that command then it will be in its own network namespace, with a different IP address, behind NAT, and it will have a randomly generated hostname. I think it makes sense to refer to the latter kind of container as a separate host in some contexts.