{"action":"created","issue":{"url":"https://api.github.com/repos/dotnet/dotnet-docker/issues/168","repository_url":"https://api.github.com/repos/dotnet/dotnet-docker","labels_url":"https://api.github.com/repos/dotnet/dotnet-docker/issues/168/labels{/name}","comments_url":"https://api.github.com/repos/dotnet/dotnet-docker/issues/168/comments","events_url":"https://api.github.com/repos/dotnet/dotnet-docker/issues/168/events","html_url":"https://github.com/dotnet/dotnet-docker/issues/168","id":193173037,"number":168,"title":"Need to make it easier to run nuget in docker image to publish builds to private repos","user":{"login":"tommed","id":13066,"avatar_url":"https://avatars.githubusercontent.com/u/13066?v=3","gravatar_id":"","url":"https://api.github.com/users/tommed","html_url":"https://github.com/tommed","followers_url":"https://api.github.com/users/tommed/followers","following_url":"https://api.github.com/users/tommed/following{/other_user}","gists_url":"https://api.github.com/users/tommed/gists{/gist_id}","starred_url":"https://api.github.com/users/tommed/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tommed/subscriptions","organizations_url":"https://api.github.com/users/tommed/orgs","repos_url":"https://api.github.com/users/tommed/repos","events_url":"https://api.github.com/users/tommed/events{/privacy}","received_events_url":"https://api.github.com/users/tommed/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":7,"created_at":"2016-12-02T17:30:03Z","updated_at":"2017-02-05T20:54:38Z","closed_at":"2016-12-08T13:40:56Z","body":"## Summary\r\n\r\nLike most (I'm sure), docker and dotnet are a great paradigm for automated build systems. However, when the end artefact of your build is one or more nuget packages, it is extremely hard to get `dotnet-docker` to publish nuget packages to a repo.\r\n\r\nThis isn't necessarily this repo's domain but, the vision of running builds on this infrastructure is no doubt a great use of this technology and it would be a crying shame if there wasn't a way to achieve the following...\r\n\r\n## Steps to reproduce the issue\r\n1. Launch `microsoft/dotnet:1.1.0-sdk-msbuild`\r\n2. Install nuget `apt-get update && apt-get install -y nuget`\r\n2. Perform a `dotnet pack -c Release MyProject.csproj`\r\n3. Now attempt to push to private repo `nuget push MyPackage.nupkg $MYTOKEN -Source $MY_PRIVATE_REPO`\r\n\r\n## Expected behavior\r\n\r\nWhen token and repo URI is correct, nuget should push to repo.\r\n\r\n## Actual behavior\r\n\r\n```\r\n﻿WARNING: No API Key was provided and no API Key could be found for 'https://www.myget.org/F/vapps-private/auth/1e0b67b4-9225-4f7b-9252-a37e00924af2/api/v2'. To save an API Key for a source use the 'setApiKey' command.\r\nPushing ViProCloud.Common 1.0.0 to 'https://www.myget.org/F/vapps-private/auth/1e0b67b4-9225-4f7b-9252-a37e00924af2/api/v2'...\r\n﻿Error getting response stream (Write: The authentication or decryption has failed.): SendFailure\r\n```\r\n\r\n## Additional information (e.g. issue happens only occasionally)\r\n\r\nI have tried to do an `apt-get update && apt-get install mono-devel` and then run the following (a documented workaround for nuget on linux):\r\n\r\n```\r\n$ mozroots --import --machine --sync\r\n$ certmgr -ssl -m https://go.microsoft.com\r\n$ certmgr -ssl -m https://nugetgallery.blob.core.windows.net\r\n$ certmgr -ssl -m https://nuget.org\r\n```\r\n\r\nHowever there are two problems here\r\n1. mozroots has huge amounts of dependencies which sucks in a docker paradigm\r\n2. `certmgr -ssl` requires a human to confirm (no force or yes flag available) and therefore breaks the automated build process\r\n\r\n## Output of `docker version`\r\n\r\n```\r\nClient:\r\n Version:      1.12.3\r\n API version:  1.24\r\n Go version:   go1.6.3\r\n Git commit:   6b644ec\r\n Built:        Wed Oct 26 23:26:11 2016\r\n OS/Arch:      windows/amd64\r\n\r\nServer:\r\n Version:      1.12.3\r\n API version:  1.24\r\n Go version:   go1.6.3\r\n Git commit:   6b644ec\r\n Built:        Wed Oct 26 23:26:11 2016\r\n OS/Arch:      linux/amd64\r\n```\r\n\r\n## Output of `docker info`\r\n\r\n```\r\nContainers: 8\r\n Running: 0\r\n Paused: 0\r\n Stopped: 8\r\nImages: 143\r\nServer Version: 1.12.3\r\nStorage Driver: aufs\r\n Root Dir: /var/lib/docker/aufs\r\n Backing Filesystem: extfs\r\n Dirs: 205\r\n Dirperm1 Supported: true\r\nLogging Driver: json-file\r\nCgroup Driver: cgroupfs\r\nPlugins:\r\n Volume: local\r\n Network: null bridge host overlay\r\nSwarm: inactive\r\nRuntimes: runc\r\nDefault Runtime: runc\r\nSecurity Options: seccomp\r\nKernel Version: 4.4.27-moby\r\nOperating System: Alpine Linux v3.4\r\nOSType: linux\r\nArchitecture: x86_64\r\nCPUs: 2\r\nTotal Memory: 958.1 MiB\r\nName: moby\r\nID: PWJP:KPSE:SRA5:DT7H:GVXE:NGKF:DKZP:I62H:JKNM:UH3S:SW2X:RU7H\r\nDocker Root Dir: /var/lib/docker\r\nDebug Mode (client): false\r\nDebug Mode (server): false\r\nUsername: tmedhurst\r\nRegistry: https://index.docker.io/v1/\r\nWARNING: No kernel memory limit support\r\nInsecure Registries:\r\n 127.0.0.0/8\r\n```\r\n"},"comment":{"url":"https://api.github.com/repos/dotnet/dotnet-docker/issues/comments/277548462","html_url":"https://github.com/dotnet/dotnet-docker/issues/168#issuecomment-277548462","issue_url":"https://api.github.com/repos/dotnet/dotnet-docker/issues/168","id":277548462,"user":{"login":"kenkendk","id":1510755,"avatar_url":"https://avatars.githubusercontent.com/u/1510755?v=3","gravatar_id":"","url":"https://api.github.com/users/kenkendk","html_url":"https://github.com/kenkendk","followers_url":"https://api.github.com/users/kenkendk/followers","following_url":"https://api.github.com/users/kenkendk/following{/other_user}","gists_url":"https://api.github.com/users/kenkendk/gists{/gist_id}","starred_url":"https://api.github.com/users/kenkendk/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kenkendk/subscriptions","organizations_url":"https://api.github.com/users/kenkendk/orgs","repos_url":"https://api.github.com/users/kenkendk/repos","events_url":"https://api.github.com/users/kenkendk/events{/privacy}","received_events_url":"https://api.github.com/users/kenkendk/received_events","type":"User","site_admin":false},"created_at":"2017-02-05T20:54:38Z","updated_at":"2017-02-05T20:54:38Z","body":"I think this can explain it:\r\nhttp://www.mono-project.com/docs/about-mono/releases/3.12.0/\r\n\r\nIf `ca-certificates-mono` does not exist, it should be possible to run:\r\n```\r\ncert-sync /etc/ssl/certs/ca-certificates.crt\r\n```"}}
{"actor":{"display_login":"kenkendk"}}