In the File menu, click Clone Repository. For more information, see " Cloning a repository from GitHub to GitHub Desktop". You can also clone a repository directly from GitHub or GitHub Enterprise. For more information, see " Managing fork behavior". Any existing forks default to contributing changes to their upstream repositories. You can choose to use your fork to contribute to the original upstream repository or to work independently on your own project. When you try to use GitHub Desktop to clone a repository that you do not have write access to, GitHub Desktop will prompt you to create a fork automatically. For more information, see " About forks." You can create a pull request to propose that maintainers incorporate the changes in your fork into the original upstream repository. To make changes without affecting the original project, you can create a separate copy by forking the repository. When you clone a repository, any changes you push to GitHub Enterprise Cloud will affect the original repository. For more information, see " Syncing your branch in GitHub Desktop." Publish repository Successful Add > Clone a repository See screenshot error1 Attempt2: Uninstalled & re-installed GitHub Desktop. If you own a repository or have write permissions, you can sync between the local and remote locations. Actual behavior Attempt1: Create a new repository on hard drive. You can create a local copy of any repository on GitHub Enterprise Cloud that you have access to by cloning the repository. You can clone or fork a repository with GitHub Desktop to create a local repository on your computer. What might be the issue here? Any suggestions, advice, or criticism is welcome.Repositories on GitHub are remote repositories. So from the Git Repo’s perspective, there should be no (networking) difference between the host and container. Could this be a “host” networking issue? I thought that when you set “host” networking, you’re essentially allowing the container to NAT behind the host’s IP address. So: I can ping the repo, but can’t pull code. Instead, it seems that when my container sends the “git clone” request, it never gets a response. The HTTP error code 503 (“Service Unavailable”) is clearly not the case: I know the Git Repo is available. I can ping the company’s git repo, but when I issue the exact same “git clone” command, this happens: sudo git clone git -branch 1234įatal: unable to access '': Received HTTP code 503 from proxy after pause is a few minutes long. Receiving objects: 100% (623/623), 6.96 MiB | 2.54 MiB/s, done.ĭrwxr-xr-x 4 root root 4096 Feb 8 15:21 in the container, its a different story. On the host, I can run a “git clone” command to pull a project off my company’s internal github repo, no problem: sudo git clone git -branch 1234 Ubuntu latest 54c9d81cbb44 6 days ago the docker-compose.yml file that creates the container note that I’m using “host” networking: version: "3.0" Could this be a host networking thing?ĭetails: My host machine is a Ubuntu 16.04 machine, with Docker and docker-compose installed: lsb_release -aĭocker version 20.10.7, build docker-compose -versionĭocker-compose version 1.17.1, build container is the current “latest” image of Ubuntu: sudo docker psĬONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMESį7586f98afcf 54c9d81cbb44 "bash" 22 hours ago Up 22 hours sudo docker image ls From the container, I issue the same “git clone” command nothing happens. Here’s the weirdness: From the host, I can do a “git clone” to pull down a code project. On the host, I’ve spun up one Ubuntu docker container. I have a weird problem: I have a Ubuntu host machine running Docker and docker-compose.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |