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:
- A local computer with a directory where the application that I want to dockerize is located
- A “docker server” running Portainer without shell/ssh access
- A place where I can upload/host the Docker images and where I can pull the images from on the “Docker server”
- 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?
Poorly
What does your economic status have to do with creating docker images?
My code ain’t the only thing that’s broke
For the littering part, just type
crontab -e
and add the following line:@daily docker system prune -a -f
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.
Yes.
All my self hosted containers are bound to some volume (since they require reading settings or databases).
Genuinely curious, what would the advantages be?
Also, what if the Linux distro does not have systemd?
The chances I am going to manage a linux distro without systemd are low, but some systems (arch for example) don’t have cron out of the box.
Not that big of a deal since it’s easy to translate them all, but that’s one of the reasons why I default to systemd/timer units.
I was just making a meme dude. Personally, I like systemd, it’s more complicated to learn, I ended up reading books to really learn it properly. There’s 100% nothing wrong with cron.
One of the reasons I like timers is journalctl integration. I can see everything in one place. Small thing.
I build, configure, and deploy them with nix flakes for maximum reproducibility. It’s the way you should be doing it for archival purposes. With this tech, you can rebuild any docker image identically to today’s in 100 years.
https://youtu.be/0uixRE8xlbY?si=NIIFyzRhXDmcU8Kh
and here’s a link to a blog post, showing how to create a docker image and rust dev environment.
https://johns.codes/blog/rust-enviorment-and-docker-build-with-nix-flakes
I knew you were going to mention nix before reading you post.
::Robert Redford nodding gif::
Nix + dockerTools.
Doesn’t even need docker, and if buitt with flakes I don’t even have to checkout the repo.
For local testing: build and run tests on whatever computer I’m developing on.
For deployment: I have a self hosted gitlab instance in a kubernetes cluster. It comes with a registry all setup. Push the project, let the cicd pipeline build, test, and deploy through staging into prod.
I use podman, and the standalone tool “buildah” can build images from dockerfiles, and the tool “skopeo” can upload it to an image repository.
I use portainer, and when I deploy an image, I write a short bash script for it.
- stop the image if running
- pull the image
- run the image
This lets me easily do updates. I have a script for each image I run, it’s less than a dozen. They’re all from public repositories.
VM with a docker build environment.
As for “littering”, a simple
docker system prune -f
after a build gets rid of most of it.pycharm + selfhosted docker registry
Docker, Jenkins, Docker-in-Docker (dind)
Nowadays, I build them locally, and upload stable releases to registry. I have in the last used GitHub runners to do it, but building locally is just easier and faster for testing.
For public projects, I use github build pipelines.
For private, I use ansible.
Maybe this would work for you?