Docker

I run a docker container and it has some outdated bits which I forked and updated. The changes need testing and no one else seems to wanna do it. For some odd reason I'm nervous about pointing the image at my repo and building from that. Am I Being Stupid? It's not like if it fails I can't just recreate the image. None of the databases are gonna be affected. So what am I anxious about?

cross-posted from: https://lazysoci.al/post/15099881

A surprise Docker update!

cross-posted from: https://lazysoci.al/post/14373856

Docker got updated.

I built my first image locally and now I'm dancing around my desk to myself in satisfaction. I was anxious AF and so that meant I had a million extra questions along the way and everyone helped me. I'm truly grateful. Thanks for teaching me/holding my hand. I can't put into words my gratitude, but truly, thank you so so much.

Was I supposed to clone the GitHub repository before trying to build the image?

I ask because I've just seen these errors

 => ERROR [2/4] COPY patches/ /tmp/patches/                                0.0s
 => CACHED [3/4] RUN   echo "**** install build packages ****" &&   apk a  0.0s
 => ERROR [4/4] COPY root/ /                                               0.0s
------
 > [2/4] COPY patches/ /tmp/patches/:
------
------
 > [4/4] COPY root/ /:
------
Dockerfile:63
--------------------
  61 |     
  62 |     # add local files
  63 | >>> COPY root/ /
  64 |     
  65 |     # ports and volumes
--------------------
ERROR: failed to solve: failed to compute cache key: failed to calculate checksum of ref 2ad57b92-028a-429f-a2de-be0e9a7f57af::cz3t2511b10hmumww1m73cse6: "/root": not found

And being as n00b as I am, I'm instantly trying to attribute the blame to me not doing something.

There's a service that I want to use, however for reasons, it no longer has any builds available. Consequently, I am thinking of building it myself. How does one go about doing that and then afterwards, how do I get it up on Docker hub? Can I just create an account and upload?

If I have

version: "3.8"

services: 
  example1:
    image: example.com/example1:latest
  ports: 8000:80
volumes: 
  - shared_example:/data
services: 
  example2:
    image: example.com/example2:latest
  ports: 8080:80
volumes: 
  - shared_example:/data

volumes:
  shared_example: 
    driver_opts: 
      type: nfs
      o: "192.100.1.100, nolock,soft,rw"
      device: ":/local/shared"

Will that slow things down or is the proper solution to have

volumes:
  shared_example1: 
    driver_opts: 
      type: nfs
      o: "192.100.1.100, nolock,soft,rw"
      device: ":/local/shared"
  shared_example2: 
    driver_opts: 
      type: nfs
      o: "192.100.1.100, nolock,soft,rw"
      device: ":/local/shared"

Or even

volumes:
  shared_example1:
  shared_example2: 
    driver_opts: 
    type: nfs
      o: "192.100.1.100, nolock,soft,rw"
      device: ":/local/shared"

cross-posted from: https://programming.dev/post/9667945

The Docker team announces the general availability of docker init, with support for multiple languages and stacks, making it simpler than ever to containerize your applications.