Don’t get harpooned by a Dockerfile that sucks
Your Docker Compose file might suck too.
I admit it! I am guilty of making Dockerfiles that suck.
We’re all guilty of being overly general in our Dockerfiles. Just look on Docker Hub or GitHub. But in some ways it might be making things less consistent across builds.
Which is fine for testing something or working to build Dockerfiles for development pipelines. But let’s look at the shortfalls and headaches we can all avoid. You never really know what something like the above will get you.
The same applies to running package manager with only package name and no version. In some instances you will want to update a package for security or bug fix purposes. But for Docker in Production you want to stipulate these things.
So first let’s stipulate the right known base image using it’s SHA256:
To get the SHA256 you can get it when you pull the intial image you’ll be using to build projects.
$ sudo docker pull debian:8.7
8.7: Pulling from library/debian
693502eb7dfb: Pull complete
Status: Downloaded newer image for debian:8.7
Now you know the exact version you will be running. Now be sure to stipulate for other packages you need to install.
RUN apt-get update && apt-get install -y \
&& rm -rf /var/lib/apt/lists/*
Now you have your Dockerfile not sucking so much for Production use!
You’ll also want to have internal Docker Registry for versioning and storing your containers once you build.
There are a lot of organizations fighting for your freedoms when it comes to digital rights. But the oldest and most effective is perhaps the Electronic Frontier Foundation (EFF).
From their site:
The Electronic Frontier Foundation is the leading nonprofit organization defending civil liberties in the digital world. Founded in 1990, EFF champions user privacy, free expression, and innovation through impact litigation, policy analysis, grassroots activism, and technology development. We work to ensure that rights and freedoms are enhanced and protected as our use of technology grows.
Even in the fledgling days of the Internet, EFF understood that protecting access to developing technology was central to advancing freedom for all. In the years that followed, EFF used our fiercely independent voice to clear the way for open source software, encryption, security research, file sharing tools, and a world of emerging technologies.
Today, EFF uses the unique expertise of leading technologists, activists, and attorneys in our efforts to defend free speech online, fight illegal surveillance, advocate for users and innovators, and support freedom-enhancing technologies.
Together, we forged a vast network of concerned members and partner organizations spanning the globe. EFF advises policymakers and educates the press and the public through comprehensive analysis, educational guides, activist workshops, and more. EFF empowers hundreds of thousands of individuals through our Action Center and has become a leading voice in online rights debates.
EFF is a donor-funded US 501(c)(3) nonprofit organization that depends on your support to continue fighting for users.
I recently came across this old article on using various text files to stay organized. In the past I have tried many ToDo apps with little success. So I have been using a slightly modified version mentioned in the article with great success. One big help is some quick and dirty aliases I added to my
.bashrc file which are all kept in a directory called “daily”. You can name them as you wish. My next move is to put them in my ownCloud sync directory.
#Daily txt files I write to for various reasons
alias todo='vim ~/Documents/daily/todo'
alias onething='vim ~/Documents/daily/one-thing/today_$(date +%Y%m%d)'
alias journal='vim ~/Documents/daily/journal/journal_$(date +%Y%m%d)'
alias writedaily='vim ~/Documents/daily/write-every-day'
alias ideas='vim ~/Documents/daily/ideas'
alias done='vim ~/Documents/daily/done'
alias actionplan='vim ~/Documents/daily/action-plan'