The package version changes are a good change and definitely generally helpful. Assuming everything else holds up, worth a shot.

In my testing the OSPF MDR debian package was bad and not building correctly to provide a valid install, which is why it was not being used. This will likely change in the somewhat near future with a shift away from OSPF MDR. A package is built and can be installed, but it is missing needed binaries.

I have not seen any issues related to using apt-get in this way. A source here notes support for this type of interaction was added in APT 1.1 (see release announcement).

Removing a file copied in a previous step doesn't have any impact on the image size, but would not hurt to remove it.

Regarding OSPF: Thanks for the insight. I assumed it was just an oversight not to use the package generated in the first stage of the Dockerfile.

I was also wondering why apt-get wasn't working for me, as I thought I had used it before for installing local packages. After your comment, I took a closer look and discovered that the issue was actually due to a typo I initially made in the quagga filename, which led apt-get to throw an Unsupported file ... error. My apologies for the confusion.

I've now reversed the changes related to OSPF and apt-get. The PR now only includes the modifications to download the CORE packages from the correct release and to remove the quagga packages after installation.