Containers

  1. Create microsoft registry and stop using foreign layers

    Currently the microsoft images for dotnet, server-core etc.use foreign layers to point to the base layers so they are pulled directly from microsoft, i believe this was done for licensing reasons.

    This causes issues running in most 'enterprise' networks where direct internet access is not allowed, the normal solution is something like nexus to proxy remote registries. Foreign layers bypasses this and workarounds like '--allow-nondistributable-artifacts' are cumbersome.

    Other companies like Oracle have created there own repos where they can host there own licensed images which is a far simpler solution (https://blogs.oracle.com/weblogicserver/the-oracle-container-registry-has-gone-live).

    Is it possible for microsoft to host…

    5 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  2. 5 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  3. Make older Visual studio versions install correctly in containers

    Currently, only the very latest installer for the Visual studio core tools installs correctly within a container. It would help if the installers for Older versions of Visual Studio (https://www.microsoft.com/en-us/download/details.aspx?id=44266 in particular) shouldn't complain that their executable "is not compatible with the version of Windows you're running." This would help make containers much more useful for running CI tests with older versions of Visual Studio. Some of the older installers even raise that error when being run outside of a container in a full Windows Server TP 4 installation.

    6 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  4. 16 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  5. Ability to "sysprep" containers

    It would be great to have a mechanism for performing some actions when a container is first created.

    One example is devops scenario where a container image is prepared, then when a new container is created from that image and started, it downloads and installs the latest version of the app.

    4 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base