michaelperel

In my experience (surface pro 4) with kernel 5.0.1, the symbolic links `/etc/systemd/system/suspend.target`, `/etc/systemd/system/suspend.target~`, `/etc/systemd/system/systemd-suspend.service`, and `/etc/systemd/system/systemd-suspend.service~` all existed after choosing yes to replace suspend with hibernate while doing setup.sh....

I think this is an excellent idea - it would make migrating to a private registry much easier. Let me know if this somewhat matches what you had in mind...

> I would expect this not to require flags and just use the docker auth config file, in the same way that `crane.Digest` works. My apologies, that was a lapse...

> I don't know that I really need the lockfile, but it seems integral to how docker-lock functions currently, and I don't think it really hurts anything to have it....

Upon second thought, I will play around with it in the next week and ping you with an update / code, but feel free to try some ideas out as...

@jonjohnsonjr I have a mvp working for the copy behavior in the branch `miperel/migrate`. It works with Dockerhub, but when testing it with Azure Container Registry, I ran into issues...

> One thing I haven't solved is how to rename images across registries. Ideally, you could mirror the structure of the source: > docker.io/library/foo -> private.example.com/library/foo > But, what if...

The way that I use the tool is: (1) Do not specify digests in Dockerfiles, instead run `docker lock generate` to record them in a Lockfile. (2) Track the Lockfile...

The point about drift is a good one, and I can see why someone would prefer to not use a separate file. I imagine the features would look something like:...

Sounds great, thanks for the background. ECR support is definitely easy to add -- I personally use ACR and left that as an open task since I do not have...