Alexandra K. Diem

Personal Website.
It's that time of year again where I start to move my anaerobic training indoors onto the #spinningbike , while I continue to run for aerobic training until I can start #langrenn #crosscountryskiing. I spent all of last winter season trying to come up with a #spinning routine that I really like, so now I decided to share it on my blog. Check the link in my bio 🔝 for the playlist plus description of the routine, and a link to my #spotify playlist. Say hi to my first potential foster failures! 😻 These two sisters got out of a situation with 60 (!) cats and are now looking for a forever home. Until then, I get to spoil the hell out of them 😊 #cat #catsofinstagram Not having to worry about anything other than whether the view out of your tent in the morning will be better here or a couple of metres over there... #spaholiday
.
.
.
#hiking #utpåtur #friluftsliv #turjenter #fjelltur #soveute #fjellsport #allemannsretten #nattinaturen #intersportnorge #salomonwmn #lofoten #moskenesøya #nowaynorway @intersportnorge My #lofoten #blog post is up! Lightning fast this time because I was good and wrote all (most) of the text during the trip. Hit the link in my bio 🔝 for a story about views and non-views on the peaks, being chased by rain clouds, spotting whale bones and live whales, and more.
.
.
.
#hiking #utpåtur #friluftsliv #turjenter #fjelltur #soveute #fjellsport #allemannsretten #lofoten #moskenesøya #nowaynorway

Clean up dangling images from Docker

I almost exclusively run FEniCS using Docker and have recently noticed that building images from Dockerfiles often results in a lot of <none>:<none> images showing up when I run docker images. This is different from images labelled the same showing up when running docker images -a (in that case they are “intermediate” images since Docker images are composed of layers).

The <none>:<none> images that show up when running docker images are references to old images after for example updating an image since updating an image does not actually update it, but creates a new image for the new version and leaves the old one dangling as a <none>:<none>. Docker does not have its own garbage collection, so this has to be done manually using the following terminal command.