Currently I’m planning to dockerize some web applications but I didn’t find a reasonably easy way do create the images to be hosted in my repository so I can pull them on my server.

What I currently have is:

  1. A local computer with a directory where the application that I want to dockerize is located
  2. A “docker server” running Portainer without shell/ssh access
  3. A place where I can upload/host the Docker images and where I can pull the images from on the “Docker server”
  4. Basic knowledge on how to write the needed Dockerfile

What I now need is a sane way to build the images WITHOUT setting up a fully featured Docker environment on the local computer.

Ideally something where I can build the images and upload them but without that something “littering Docker-related files all over my system”.

Something like a VM that resets on every start maybe? So … build the image, upload to repository, close the terminal window, and forget that anything ever happened.

What is YOUR solution to create and upload Docker images in a clean and sane way?

  • orizuru@lemmy.sdf.orgEnglish
    10·
    1 year ago

    For the littering part, just type crontab -e and add the following line:

    @daily docker system prune -a -f
        • vegetaaaaaaa@lemmy.worldEnglish
          2·
          1 year ago

          run docker without sudo.

          Doing that, you effectively give the user account root access without password

          docker run --volume /etc:/host_etc debian /bin/bash -> can read/write anything below the host’s /etc directory, including shadow file, etc.

          • orizuru@lemmy.sdf.orgEnglish
            2·
            1 year ago

            True.

            But I assume OP was already running docker from that user, so they are comfortable with those permissions.

            Maybe should have made it clearer. Added to my other post. Thanks!

    • vegetaaaaaaa@lemmy.worldEnglish
      2·
      1 year ago

      Careful this will also delete your unused volumes (not attached to a running container because it is stopped for whatever reason counts as unused). For this reason alone, always use bind mounts for volumes you care about.

      • orizuru@lemmy.sdf.orgEnglish
        1·
        1 year ago

        Yes.

        All my self hosted containers are bound to some volume (since they require reading settings or databases).

      • orizuru@lemmy.sdf.orgEnglish
        2·
        1 year ago

        Genuinely curious, what would the advantages be?

        Also, what if the Linux distro does not have systemd?