Closed deviantony closed 5 years ago
Thanks @deviantony that's good to know that you're using this tool. I'm using this tool with 1809 images with a little trick as I hadn't the time to dig deeper into the issue. The MCR is more hidden what works and what does not, some API calls are disabled compared to Docker Hub. I don't know exactly if that is the problem here, but the following trick works for me.
Look at eg. https://github.com/StefanScherer/whoami/pull/10/files I tag and push the mcr images to an own repository on Docker Hub and then use this tag for the rebase. No Windows image is pushed to Docker Hub, only the metadata. It was much easier to fix it this way.
After each Patch Tuesday I have to push a new tag. I just did that for the latest like this:
docker pull mcr.microsoft.com/windows/nanoserver:1809
docker manifest inspect mcr.microsoft.com/windows/nanoserver:1809
docker tag mcr.microsoft.com/windows/nanoserver:1809 stefanscherer/nanoserver:10.0.17763.194
docker push stefanscherer/nanoserver:10.0.17763.194
@deviantony with #6 merged and published it should work now.
I just tried this one:
rebase-docker-image portainer/portainer:windows-amd64 -t stefscherer/reb1:windows1809-amd64 -b mcr.microsoft.com/windows/nanoserver:1809 --verbose
Great, thanks for the update.
Hi @StefanScherer, hope you're doing well !
We're still using this tool to build our different Windows images for Portainer but it seems that we have an issue with the Windows 1809 image.
Based on the
mcr.microsoft.com/windows/nanoserver:1809
image. Do you have any recommendations for using this tool with the latest 1809 image?Thanks again.