Error : Unable to upload into a virtual repository without default local deployment configured (Docker...





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







0















I am trying to push a docker image to a repository.



But I am constantly getting the following error -
enter image description here



Steps followed -




  1. Logged in to " docker login https://docker.wdf.sap.corp:50000/ "


  2. Got authorized with my username/password


  3. Created a local docker image


  4. Did a docker push. - '' docker push docker.wdf.sap.corp:50000/taaas/ws-python:latest ''











share|improve this question





























    0















    I am trying to push a docker image to a repository.



    But I am constantly getting the following error -
    enter image description here



    Steps followed -




    1. Logged in to " docker login https://docker.wdf.sap.corp:50000/ "


    2. Got authorized with my username/password


    3. Created a local docker image


    4. Did a docker push. - '' docker push docker.wdf.sap.corp:50000/taaas/ws-python:latest ''











    share|improve this question

























      0












      0








      0


      1






      I am trying to push a docker image to a repository.



      But I am constantly getting the following error -
      enter image description here



      Steps followed -




      1. Logged in to " docker login https://docker.wdf.sap.corp:50000/ "


      2. Got authorized with my username/password


      3. Created a local docker image


      4. Did a docker push. - '' docker push docker.wdf.sap.corp:50000/taaas/ws-python:latest ''











      share|improve this question














      I am trying to push a docker image to a repository.



      But I am constantly getting the following error -
      enter image description here



      Steps followed -




      1. Logged in to " docker login https://docker.wdf.sap.corp:50000/ "


      2. Got authorized with my username/password


      3. Created a local docker image


      4. Did a docker push. - '' docker push docker.wdf.sap.corp:50000/taaas/ws-python:latest ''








      docker artifactory jfrog-cli






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Jan 3 at 14:59









      Ankur BagAnkur Bag

      193




      193
























          1 Answer
          1






          active

          oldest

          votes


















          3














          Most likely the virtual repository you're trying to push to only has remote repositories configured as the target to be able to push to. I tried to replicate your issue on my own Artifactory instance using a two different docker repositories (both virtual):



          For the first I have both local and remote repositories configured (the configured targets are docker-local, bintray-docker-remote, docker-remote)



          $ docker tag mynewimage:latest myartifactory.server/docker/mynewimage
          $ docker push myartifactory.server/docker/mynewimage
          The push refers to repository [myartifactory.server/docker/mynewimage]
          7bff100f35cb: Layer already exists
          latest: digest: sha256:3d2e482b82608d153a374df3357c0291589a61cc194ec4a9ca2381073a17f58e size: 528


          The second repository only has remote repositories configured (docker-remote)



          $ docker tag mynewimage:latest myartifactory.server/newdocker/mynewimage:latest
          $ docker push myartifactory.server/newdocker/mynewimage:latest
          The push refers to repository [myartifactory.server/newdocker/mynewimage]
          7bff100f35cb: Retrying in 1 second
          unknown: Unable to upload into a virtual repository without default local deployment configured.


          So with the second one I have the exact same issue as you have. You can see the configured repositories on your Artifactory server on https://your-artifactory-server/artifactory/webapp/#/admin/repositories/virtual






          share|improve this answer
























          • Thanks for the response.

            – Ankur Bag
            Jan 4 at 18:38












          Your Answer






          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "1"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54024794%2ferror-unable-to-upload-into-a-virtual-repository-without-default-local-deploym%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          3














          Most likely the virtual repository you're trying to push to only has remote repositories configured as the target to be able to push to. I tried to replicate your issue on my own Artifactory instance using a two different docker repositories (both virtual):



          For the first I have both local and remote repositories configured (the configured targets are docker-local, bintray-docker-remote, docker-remote)



          $ docker tag mynewimage:latest myartifactory.server/docker/mynewimage
          $ docker push myartifactory.server/docker/mynewimage
          The push refers to repository [myartifactory.server/docker/mynewimage]
          7bff100f35cb: Layer already exists
          latest: digest: sha256:3d2e482b82608d153a374df3357c0291589a61cc194ec4a9ca2381073a17f58e size: 528


          The second repository only has remote repositories configured (docker-remote)



          $ docker tag mynewimage:latest myartifactory.server/newdocker/mynewimage:latest
          $ docker push myartifactory.server/newdocker/mynewimage:latest
          The push refers to repository [myartifactory.server/newdocker/mynewimage]
          7bff100f35cb: Retrying in 1 second
          unknown: Unable to upload into a virtual repository without default local deployment configured.


          So with the second one I have the exact same issue as you have. You can see the configured repositories on your Artifactory server on https://your-artifactory-server/artifactory/webapp/#/admin/repositories/virtual






          share|improve this answer
























          • Thanks for the response.

            – Ankur Bag
            Jan 4 at 18:38
















          3














          Most likely the virtual repository you're trying to push to only has remote repositories configured as the target to be able to push to. I tried to replicate your issue on my own Artifactory instance using a two different docker repositories (both virtual):



          For the first I have both local and remote repositories configured (the configured targets are docker-local, bintray-docker-remote, docker-remote)



          $ docker tag mynewimage:latest myartifactory.server/docker/mynewimage
          $ docker push myartifactory.server/docker/mynewimage
          The push refers to repository [myartifactory.server/docker/mynewimage]
          7bff100f35cb: Layer already exists
          latest: digest: sha256:3d2e482b82608d153a374df3357c0291589a61cc194ec4a9ca2381073a17f58e size: 528


          The second repository only has remote repositories configured (docker-remote)



          $ docker tag mynewimage:latest myartifactory.server/newdocker/mynewimage:latest
          $ docker push myartifactory.server/newdocker/mynewimage:latest
          The push refers to repository [myartifactory.server/newdocker/mynewimage]
          7bff100f35cb: Retrying in 1 second
          unknown: Unable to upload into a virtual repository without default local deployment configured.


          So with the second one I have the exact same issue as you have. You can see the configured repositories on your Artifactory server on https://your-artifactory-server/artifactory/webapp/#/admin/repositories/virtual






          share|improve this answer
























          • Thanks for the response.

            – Ankur Bag
            Jan 4 at 18:38














          3












          3








          3







          Most likely the virtual repository you're trying to push to only has remote repositories configured as the target to be able to push to. I tried to replicate your issue on my own Artifactory instance using a two different docker repositories (both virtual):



          For the first I have both local and remote repositories configured (the configured targets are docker-local, bintray-docker-remote, docker-remote)



          $ docker tag mynewimage:latest myartifactory.server/docker/mynewimage
          $ docker push myartifactory.server/docker/mynewimage
          The push refers to repository [myartifactory.server/docker/mynewimage]
          7bff100f35cb: Layer already exists
          latest: digest: sha256:3d2e482b82608d153a374df3357c0291589a61cc194ec4a9ca2381073a17f58e size: 528


          The second repository only has remote repositories configured (docker-remote)



          $ docker tag mynewimage:latest myartifactory.server/newdocker/mynewimage:latest
          $ docker push myartifactory.server/newdocker/mynewimage:latest
          The push refers to repository [myartifactory.server/newdocker/mynewimage]
          7bff100f35cb: Retrying in 1 second
          unknown: Unable to upload into a virtual repository without default local deployment configured.


          So with the second one I have the exact same issue as you have. You can see the configured repositories on your Artifactory server on https://your-artifactory-server/artifactory/webapp/#/admin/repositories/virtual






          share|improve this answer













          Most likely the virtual repository you're trying to push to only has remote repositories configured as the target to be able to push to. I tried to replicate your issue on my own Artifactory instance using a two different docker repositories (both virtual):



          For the first I have both local and remote repositories configured (the configured targets are docker-local, bintray-docker-remote, docker-remote)



          $ docker tag mynewimage:latest myartifactory.server/docker/mynewimage
          $ docker push myartifactory.server/docker/mynewimage
          The push refers to repository [myartifactory.server/docker/mynewimage]
          7bff100f35cb: Layer already exists
          latest: digest: sha256:3d2e482b82608d153a374df3357c0291589a61cc194ec4a9ca2381073a17f58e size: 528


          The second repository only has remote repositories configured (docker-remote)



          $ docker tag mynewimage:latest myartifactory.server/newdocker/mynewimage:latest
          $ docker push myartifactory.server/newdocker/mynewimage:latest
          The push refers to repository [myartifactory.server/newdocker/mynewimage]
          7bff100f35cb: Retrying in 1 second
          unknown: Unable to upload into a virtual repository without default local deployment configured.


          So with the second one I have the exact same issue as you have. You can see the configured repositories on your Artifactory server on https://your-artifactory-server/artifactory/webapp/#/admin/repositories/virtual







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Jan 3 at 16:57









          retgitsretgits

          6041310




          6041310













          • Thanks for the response.

            – Ankur Bag
            Jan 4 at 18:38



















          • Thanks for the response.

            – Ankur Bag
            Jan 4 at 18:38

















          Thanks for the response.

          – Ankur Bag
          Jan 4 at 18:38





          Thanks for the response.

          – Ankur Bag
          Jan 4 at 18:38




















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Stack Overflow!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54024794%2ferror-unable-to-upload-into-a-virtual-repository-without-default-local-deploym%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          android studio warns about leanback feature tag usage required on manifest while using Unity exported app?

          SQL update select statement

          'app-layout' is not a known element: how to share Component with different Modules