Alexandra K. Diem

Personal Website.
I love a great opportunity to make a #birthdaycake, especially when it's an opportunity to go to town on your construction skills! My Norwegian flag cake for Norway's constitution day #syttendemai #17mai is one of my absolute favourites πŸ°πŸ‡³πŸ‡΄. If you're curious about how it's made check out the link to my blog post πŸ”
.
#nowaynorway #gratulerermeddagen Gratulerer sΓ₯ mye med dagen Norge!
.
Happy constitution day Norway! #nowaynorway
.
πŸ˜˜πŸ‡³πŸ‡΄ This crowd makes the 5 am wake-up call easy peasy!
.
#Repost @bikelicious.cc (@get_repost)
・・・
The early birds rule the street. It’s a fact! Oslo Dawn Patrol in action on Tuesday. Things are getting serious now! #OsloDawnPatrol
.
.
.
#earlybird #landevei #vegtur #wymtm #sykkelmagasinet #norsksykling #sykkelglede #cycling #cykling #stakkarsoss #visitoslo #freshairclub #pedaldamnit #rideyourbike #foreverbuttphotos #notbeachroad #outsideisfree #roadslikethese #fromwhereiride #thecyclingculture #beautyofcycling #goroadcycling #thankyoucycling The view that made the sprinter fall in love with climbing #nowaynorway
.
#worldbybike #outsideisfree #fromwhereiride #womencycling

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.