16:36:18 # Life Book reading club: The Book Of Tea. Had a session introducing the Book Of Tea. It's a nice introductory book written in 1906, by Okakura Kakuzo, while he was working for Boston Museum, in English. Although it is old and feels too dramatic in how he expresses things, the book covers many aspects of Teaism and good introduction to the many aspects. The book is avilable on the Project Gutenberg.
08:35:00 # Life gcloud builds submit failed for me today with a mysterious error message. kaniko issue?
gcr.io/kaniko-project/executor:latest INFO[0000] Resolved base name debian to debian INFO[0000] Resolved base name debian to debian INFO[0000] Retrieving image manifest debian INFO[0001] Retrieving image manifest debian INFO[0001] Built cross stage deps: map[] INFO[0001] Retrieving image manifest debian INFO[0002] Retrieving image manifest debian INFO[0002] Checking for cached layer gcr.io/tokyodebian/image/cache:88873a72c8798e7e8744bd668a4fe942e03fe903bfe4d69703c00b13f70943a9... INFO[0003] No cached layer found for cmd RUN apt-get clean && apt-get update && apt-get install -yq clang make tar zip && apt-get clean INFO[0003] Unpacking rootfs as cmd RUN apt-get clean && apt-get update && apt-get install -yq clang make tar zip && apt-get clean requires it. error building image: error building stage: failed to get filesystem from image: error removing var/run to make way for new symlink: unlinkat /var/run/docker.sock: device or resource busy ERROR ERROR: build step 0 "gcr.io/kaniko-project/executor:latest" failed: exit status 1 ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- ERROR: (gcloud.builds.submit) build f6a8f12e-e686-4850-9094-52746e11e742 completed with status "FAILURE"
steps:
- name: 'gcr.io/kaniko-project/executor:latest'
args:
- --cache-repo=gcr.io/$PROJECT_ID/image/cache
- --cache=true
- --no-push
10:19:16 # Life FUSE behaving differently from what I expected. I thought after RELEASE there's no READ, but apparently if you do mmap and close and read, it causes a READ after RELEASE. Having read through the documentation it doesn't seem like it's expected behavior. Maybe I am dreaming. I can make it reliably happen if I do sleep(1) in OPEN handler.