>> Maybe it's too new?
>
> The actual error message seems to suggest that may be the case -
> about linked layers etc?
Actually, it was not too new, it's just that the method of creating a
Docker container has changed over the year.
> Anyway, on the "too new" front, I am not sure it makes any sense to
> have an explicitly dated image, when you do apt-get update inside...
Maybe, I don't have an opinion to that. I simply tried to update
everything to be the same as before, just with a newer base image.
Werner
