Change: Rewrite Dockerhost scripts in Go

[CGoodwin90]

In conjunction with uselagoon/lagoon-charts#561

WIP - Rewrote in Go

• docker-host/update-images.sh
• docker-host/prune-images.sh
• docker-host/remove-exited.sh

Moved cmd directive to execute in Go.

[shreddedbacon]

Minor changes to errors, otherwise all good (considering the below around filtering)

[shreddedbacon]

I see you're just doing the filter to split by pipe. Even though the previous grep was doing regex pattern matching, splitting by pipe will solve the problem. But if other users have deployed the existing chart and are seeing that it does regex, then this filter will still fail.

I see the thought process on this, but being regex I could put uselagoon|amazeeio|*.io and the previous grep filter would work. But if I was to put that into this filter that docker is using, it would maybe not work properly?

I think as this is an entirely new method of doing filtering, the old method of pulling in the filter from the helmchart should be deprecated.

So instead of doing this we should probably change the chart to be, and make it clear these must be full repositories (or even the full filter value of *lagoon/*:*, this would probably be best honestly, then you can add any filter you want without being bound to the fmt of *%s/*:*)

repositoriesToUpdate: 
	- amazeeio
	- uselagoon
## OR
repositoriesToUpdate: 
	- amazeeio/*:*
	- *lagoon/*:*

And then updating the deployment to do something like this

        - name: REPOSITORY_TO_UPDATE
          value: {{ join "|" .Values.dockerHost.repositoriesToUpdate | quote }}

[shreddedbacon]

Minor thing in the dockerfile for the change to filters

[shreddedbacon]

Seems good to me

[tobybellwood]

Also seeing this message - may be worth disabling authentication check in here

time="2023-08-17T05:42:46.173119194Z" level=warning msg="Please consider generating tls certificates with client validation to prevent exposing unauthenticated root access to your network" host="tcp://0.0.0.0:2375"
time="2023-08-17T05:42:46.173220943Z" level=warning msg="You can override this by explicitly specifying '--tls=false' or '--tlsverify=false'" host="tcp://0.0.0.0:2375"
time="2023-08-17T05:42:46.173282740Z" level=warning msg="Support for listening on TCP without authentication or explicit intent to run without authentication will be removed in the next release" host="tcp://0.0.0.0:2375"

[tobybellwood]

ok @CGoodwin90 - this is back!

Couple of notes:

• Instead of having the danglingFilter as a boolean option that runs after the pruneImagesSchedule - it should run on a separate schedule on its own, just to remove dangling images
• we'll need to do a go modules update to this, and it will break some code - likely github.com/docker/docker

# docker-host
./main.go:101:54: undefined: types.ContainerListOptions
./main.go:111:59: undefined: types.ContainerRemoveOptions
./main.go:128:55: undefined: types.ImageListOptions
./main.go:148:51: undefined: types.ImagePullOptions
./main.go:161:56: undefined: types.ImageListOptions

[CGoodwin90]

ok @CGoodwin90 - this is back!

Couple of notes:

• Instead of having the danglingFilter as a boolean option that runs after the pruneImagesSchedule - it should run on a separate schedule on its own, just to remove dangling images
• we'll need to do a go modules update to this, and it will break some code - likely github.com/docker/docker

# docker-host
./main.go:101:54: undefined: types.ContainerListOptions
./main.go:111:59: undefined: types.ContainerRemoveOptions
./main.go:128:55: undefined: types.ImageListOptions
./main.go:148:51: undefined: types.ImagePullOptions
./main.go:161:56: undefined: types.ImageListOptions

Cool, I'll take a look at it!