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?

1 point
*

Oh hey.

Iā€™ve done this in a ton of different ways.

Manually, viis GitLab CI/CD, CI/CD with Kaniko.

My current favourite though is Kubler; I did a write-up for Lemmy a little while ago: https://lemmy.srcfiles.zip/post/32334

permalink
report
reply
1 point

For private project free gitlab account. At work self hosted gitlab.

permalink
report
reply
1 point

For public projects, I use github build pipelines.

For private, I use ansible.

permalink
report
reply
6 points

Gitlab has a great set of CI tools for deploying docker images, and includes an internal registry of images automatically tied to your repo and available in CI.

permalink
report
reply

Selfhosted

!selfhosted@lemmy.world

Create post

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you donā€™t control.

Rules:

  1. Be civil: weā€™re here to support and learn from one another. Insults wonā€™t be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If itā€™s not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Donā€™t duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (donā€™t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

Community stats

  • 5.3K

    Monthly active users

  • 3.7K

    Posts

  • 81K

    Comments