It looks like the tags were changed recently which caused a breaking change with out build/application.
We have been using node:dubnium for the past week with no problems, and then today our builds failed due to the docker container.
It appears the node:dubnium was changed to point to debian stretch instead of debian jessie. Jessie had some files that our application depended on that stretch does not.
We have fixed the issue for our build by switching to use node:dubnium-jessie instead.
Not sure if this was an intended change (or if we were using tags wrong). Just figured I should let people know that a tag change had some repercussions.
It looks like the tags were changed recently which caused a breaking change with out build/application.
We have been using node:dubnium for the past week with no problems, and then today our builds failed due to the docker container.
It appears the node:dubnium was changed to point to debian stretch instead of debian jessie. Jessie had some files that our application depended on that stretch does not.
We have fixed the issue for our build by switching to use node:dubnium-jessie instead.
Not sure if this was an intended change (or if we were using tags wrong). Just figured I should let people know that a tag change had some repercussions.