You are overanalyzing this. It&#39;s just a simple typo. Should be:

    RUN apt-get update &amp;&amp; \
        apt-get upgrade -y &amp;&amp; \
        apt-get install -y git

Those are 3 separate commands.

Some thoughts:

* 1. Replace `apt-get install git` with `apt-get install --assume-yes git`.  Without the `--assume-yes` it will prompt you for confirmation, which you are unable to give and it will be smart enough to figure that out and assume you meant &quot;NO&quot;.
* 2. You added the ssh key, but did you confirm it was `0600`.  I would just copy it and specifically `chmod 0600 ~/.ssh/id_rsa` to be sure.

Overall, your Dockerfile looks very clever and I got some fresh ideas from reading it.

For those working with `alpine` images, `RUN apk add --no-cache git` did the trick for me.

Running Visual Studio Community 2017. Created a WebAPI project, have a controller class in there, with some basic stuff, but when I go to run in debug mode, I get the following error on my breakpoints, and I haven&#39;t the foggiest idea why.

`The breakpoint will not currently be hit. Breakpoints set but not yet bound.`

I&#39;ve seen a few answers here and there, but they don&#39;t help, or they&#39;re about Visual Studio Code, which I am definitely not using. 

I found [this][1], but it doesn&#39;t tell me what to do about my problem. How do I fix this issue?



  [1]: https://docs.microsoft.com/en-us/visualstudio/extensibility/debugger/binding-breakpoints

Breakpoints set but not yet bound in Visual Studio

TL;DR. I&#39;m lost as to how to access the data after deleting a PVC, as well as why PV wouldn&#39;t go away after deleting a PVC.

Steps I&#39;m taking:

1. created a disk in GCE manually:

        gcloud compute disks create --size 5Gi disk-for-rabbitmq --zone europe-west1-b

2. ran:
  
        kubectl apply -f /tmp/pv-and-pvc.yaml

    with the following config:

        # /tmp/pv-and-pvc.yaml
        apiVersion: v1
        kind: PersistentVolume
        metadata:
          name: pv-for-rabbitmq
        spec:
          accessModes:
          - ReadWriteOnce
          capacity:
            storage: 5Gi
          gcePersistentDisk:
            fsType: ext4
            pdName: disk-for-rabbitmq
          persistentVolumeReclaimPolicy: Delete
          storageClassName: standard
        ---
        apiVersion: v1
        kind: PersistentVolumeClaim
        metadata:
          name: pvc-for-rabbitmq
        spec:
          accessModes:
          - ReadWriteOnce
          resources:
            requests:
              storage: 5Gi
          storageClassName: standard
          volumeName: pv-for-rabbitmq

3. deleted a PVC manually (on a high level: I&#39;m simulating a disastrous scenario here, like accidental deletion or misconfiguration of a `helm` release):

        kubectl delete pvc pvc-for-rabbitmq

At this point I see the following:

    $ kubectl get pv
    NAME              CAPACITY   ACCESS MODES   RECLAIM POLICY   STATUS     CLAIM                      STORAGECLASS   REASON   AGE
    pv-for-rabbitmq   5Gi        RWO            Delete           Released   staging/pvc-for-rabbitmq   standard                8m
    $

&gt; A side question, just improve my understanding: **why PV is still there, even though it has a reclaim policy set to `Delete`?** Isn&#39;t this what the [docs](https://kubernetes.io/docs/concepts/storage/persistent-volumes/#delete) say for the `Delete` reclaim policy?

Now if I try to re-create the PVC to regain access to the data in PV:

    $ kubectl apply -f /tmp/pv-and-pvc.yaml
    persistentvolume &quot;pv-for-rabbitmq&quot; configured
    persistentvolumeclaim &quot;pvc-for-rabbitmq&quot; created
    $

I still get this for `pv`s, e.g. a PV is stuck in `Released` state:

    $
    kubectl get pv
    NAME                                       CAPACITY   ACCESS MODES   RECLAIM POLICY   STATUS     CLAIM                             STORAGECLASS   REASON    AGE
    pv-for-rabbitmq                            5Gi        RWO            Delete           Released   staging/pvc-for-rabbitmq          standard                 15m
    $

...and I get this for `pvc`s:

    $
    kubectl get pvc
    NAME               STATUS    VOLUME            CAPACITY   ACCESS MODES   STORAGECLASS   AGE
    pvc-for-rabbitmq   Pending   pv-for-rabbitmq   0                         standard       1m
    $

Looks like my PV is stuck in `Released` status, and PVC cannot access the PV which is not in `Available` status.

So, why the same PV and PVC cannot be friends again? **How do I make a PVC to regain access to data in the existing PV?**

What to do with Released persistent volume?

I&#39;m trying to pull the repository I&#39;m working on while doing a docker build, so I followed [this tutorial][1] so I added in my `Dockerfile`

    # this is our first build stage, it will not persist in the final image
    FROM ubuntu as intermediate
    
    # install git
    RUN apt-get update \
        apt-get upgrade \
        apt-get install git
    
    # add credentials on build
    RUN mkdir ~/.ssh &amp;&amp; ln -s /run/secrets/host_ssh_key ~/.ssh/id_rsa
    
    # make sure your domain is accepted
    RUN touch /root/.ssh/known_hosts
    RUN ssh-keyscan github.org &gt;&gt; /root/.ssh/known_hosts
    
    RUN git clone git@github.com:my-repo/myproject.git
    
    FROM ubuntu
    # copy the repository form the previous image
    COPY --from=intermediate /your-repo /srv/your-repo

In my `docker-compose.yml` I added

    secrets:
      host_ssh_key:
        file: ~/.ssh/id_rsa

And I&#39;m adding

    secrets:
      - host_ssh_key

In one of the service.

Since this is only for my local use (I don&#39;t plan on deploying or using this for the production, I just want to test it out) it&#39;s fine to use it this way - if it&#39;ll work because currently the build fails at the git install stage with error

&gt; E: The update command takes no arguments
&gt;
&gt; ERROR: Service &#39;web&#39; failed to build: The command &#39;/bin/sh -c apt-get update  apt-get upgrade     apt-get install git&#39; returned a non-zero code: 100

What am I missing?

  [1]: https://vsupalov.com/build-docker-image-clone-private-repo-ssh-key/

git install fails in Dockerfile

I'm trying to pull the repository I'm working on while doing a docker build, so I followed <a href="https://vsupalov.com/build-docker-image-clone-private-repo-ssh-key/" target="_blank" rel="noopener noreferrer">this tutorial</a> so I added in my <code>Dockerfile</code>
<pre><code class="hljs language-bash"># this is our first build stage, it will not persist in the final image
FROM ubuntu as intermediate

# install git
RUN apt-get update \
 apt-get upgrade \
 apt-get install git

# add credentials on build
RUN mkdir ~/.ssh &#x26;&#x26; ln -s /run/secrets/host_ssh_key ~/.ssh/id_rsa

# make sure your domain is accepted
RUN touch /root/.ssh/known_hosts
RUN ssh-keyscan github.org >> /root/.ssh/known_hosts

RUN git clone git@github.com:my-repo/myproject.git

FROM ubuntu
# copy the repository form the previous image
COPY --from=intermediate /your-repo /srv/your-repo
</code></pre>
In my <code>docker-compose.yml</code> I added
<pre><code class="hljs language-yaml">secrets:
 host_ssh_key:
 file: ~/.ssh/id_rsa
</code></pre>
And I'm adding
<pre><code class="hljs language-makefile">secrets:
 - host_ssh_key
</code></pre>
In one of the service.
Since this is only for my local use (I don't plan on deploying or using this for the production, I just want to test it out) it's fine to use it this way - if it'll work because currently the build fails at the git install stage with error
> E: The update command takes no arguments
>
> ERROR: Service 'web' failed to build: The command '/bin/sh -c apt-get update apt-get upgrade apt-get install git' returned a non-zero code: 100
What am I missing?

I&#39;m new to git and I&#39;m trying to commit my first changes on a Windows machine. However, when I type in `$git commit` it takes me to a different screen than any online tutorials show or than what is mentioned in [Pro Git][1]. No online searching yields an explanation of how to use this screen, either.

The screen looks like this: [![The git commit screen I&#39;m having trouble with][2]][2]

I have tried every key on the keyboard, but nothing seems to actually **do** the commit. Also there are all these little help options in green at the bottom of the screen that seem to be giving commands, but when I press the buttons they show it just types them into the commit message. What are those help options and how do I use them?

Everyone else seems to be using something called &quot;vim&quot; which I believe I chose not to install when installing Git because I thought the Windows console was fine.

*So how do I actually commit and what are those green commands at the bottom of the screen?* Thanks!


  [1]: https://git-scm.com/book/en/v2
  [2]: https://i.stack.imgur.com/qobmR.png

How to commit a change in git when git commit opens Nano?

Suppose that I would like to implement a fix to a project of someone else. That project resides on GitHub.

I could create a fork on GitHub and implement the fix.

However, I would like to create my fork on GitLab rather than on GitHub.

Is that possible? How?

I have read this article:
https://about.gitlab.com/2016/12/01/how-to-keep-your-fork-up-to-date-with-its-origin/

Anyway, I am not sure what should I do in my case.

 - Should I just create a fork on GitLab of the project from GitHub somehow?
 - Or should I create a mirror on GitLab of the project from GitHub?
 - Or should I create a mirror on GitLab and then fork the mirror?
 - Or should I do  something completely different?

What is the correct approach.

Thanks.

**UPDATE**

Repository mirroring on GitLab does not make sense probably. I can create a mirror of MY GitHub repository on GitLab but I cannot create a mirror of a repository of someone else.

https://docs.gitlab.com/ee/workflow/repository_mirroring.html

This is what I have done so far:

I have cloned the original GitHub project to my local machine. I have commited the fix to a new branch in my local repository. I have created an empty project on GitLab. I have set origin in my local repository to that empty project on GitLab and pushed both branches to GitLab. I have set upstream in my local repository to the GitHub repository.

When I want to get new commits from the original GitHub repository to the repository on GitLab (i.e. sync the repositories), I can do this using my local repo as an intermediate step. However, there is no direct connection between the repo on GitHub and the repo on GitLab. Is my setup correct? Is there any difference if I make a fork on GitHub?

Forking Git repository from GitHub to GitLab

To note, I&#39;m on Oh-My-Zsh and git 2.17. Whenever I type in git branch, instead of showing me the branches of my git, it shows something like this:

    ~
    ~
    ~
    ~
    ~
    (END)

I can quit this by pressing &#39;q&#39; on my keyboard, but I&#39;m still confused as to why this is appearing.

git branch ~(END) on terminal?

I was trying to compare two commits on the same branch (master in this case) in BitBucket and did not find a good answer in any forum, so decided to try their client, SourceTree to see if installing it locally would help and it did.

Therefore, thought it might be useful to add question and answer here. 

How to compare two commits in BitBucket?

I had a bunch of staged and unstaged changes and I wanted to quickly switch to another branch and then switch back.

So I staged my changes using:

    $ git stash push -a

(In hindsight I probably could have used `--include-untracked` instead of `--all`)

Then when I went to pop the stash I get a whole lot of errors along the lines of:

    $ git stash pop
    foo.txt already exists, no checkout
    bar.txt already exists, no checkout
    ...
    Could not restore untracked files from stash entry

There doesn&#39;t seem to be any changes restored from the stash.

I also tried `$ git stash branch temp` but that shows the same errors.

I did figure out a way around this which was to use:

    $ git stash show -p | git apply

Disaster averted for now but this raises some questions.

Why did this error happen in the first place and how do I avoid it next time?

Why does git stash pop say that it could not restore untracked files from stash entry?

How to be with orphan images when you have 2 independent projects and you want them to work at the same time or at least to build running `docker-compose up -d` without `--remove-orphans` flag when images are already built for another project. 

docker compose file1:

    version: &#39;2&#39;
    services:
      applications:
        image: tianon/true
        volumes:
          - ../../:/var/www/vhosts/project1
      nginx:
        build: ./images/nginx
        image: project1/nginx:latest
        ports:
          - &quot;80:80&quot;
        volumes_from:
          -  applications
        networks:
          appnet:
            aliases:
              - project1.app
              - admin.project1.app
      php:
        image: project1/php:latest
        ports:
          - &quot;7778:7778&quot;
        build: 
          context: ./images/php
          dockerfile: Dockerfile
        volumes_from:
          -  applications
        networks:
          -  appnet
      mysql:
        image: project1/mysql:latest
        build: ./images/mysql
        environment:
          MYSQL_ROOT_PASSWORD: secret
        volumes:
          -  mysqldata:/var/lib/mysql
        networks:
          -  appnet
        ports:
          - &quot;33066:3306&quot;
     workspace:
        image: project1/workspace:latest
        build:
          context: ./images/workspace
        volumes_from:
          - applications
        working_dir: /var/www/vhosts/project1
        networks:
          -  appnet
    networks:
      appnet:
        driver: &quot;bridge&quot;
    volumes:
       mysqldata:
        driver: &quot;local&quot;



the second docker compose file:


    version: &#39;2&#39;
    services:
      project2_applications:
        image: tianon/true
        volumes:
          - ../../:/var/www/vhosts/project2
      project2_nginx:
        build: ./images/nginx
        image: project2/nginx:latest
        ports:
          - &quot;8080:80&quot;
        volumes_from:
          -  project2_applications
        networks:
          project2_appnet:
            aliases:
              - project2.app
              - admin.project2.app
      project2_php:
        image: project2/php:latest
        ports:
          - &quot;7777:7777&quot;
        build: 
          context: ./images/php
          dockerfile: Dockerfile
        volumes_from:
          -  project2_applications
        networks:
          -  project2_appnet
      project2_mysql:
        image: project2/mysql:latest
        build: ./images/mysql
        environment:
          MYSQL_ROOT_PASSWORD: secret
        volumes:
          -  project2_mysqldata:/var/lib/mysql
        networks:
          -  project2_appnet
        ports:
          - &quot;33067:3306&quot;
      project2_workspace:
        image: project2/workspace:latest
        build:
          context: ./images/workspace
        volumes_from:
          - project2_applications
        working_dir: /var/www/vhosts/videosite
        networks:
          -  project2_appnet
    networks:
      project2_appnet:
        driver: &quot;bridge&quot;
    volumes:
       project2_mysqldata:
        driver: &quot;local&quot;


And now when I have already built project1 and trying to run `docker-compose up -d` for the second project I see warning:

&gt; WARNING: Found orphan containers (docker_workspace_1, docker_nginx_1, docker_php_1, docker_mysql_1, docker_memcached_1) for this project. If you removed or renamed this service in your compose file, you can run this command with the `--remove-orphans` flag to clean it up.

I have a supposition that it&#39;s because container names for project1 should be more specific and I need to add some prefixes like I&#39;m doing for project2, but project1 is in use by many other developers and I do not want to change it.

**Is there any way to turn off orphan check?**

And the second thing: is just a warning message but for some reason, after it appearing compose is failing with error:

&gt; ERROR: Encountered errors while bringing up the project. 

And to make it work I need to run `docker-compose up -d --remove-orphans`

docker compose orphan containers warning

From what I understand about Docker, it&#39;s a tool used for virtual environments. In their lingo, its called &quot;containerization&quot;. This is more or less what Python&#39;s virtualenv does. However, you can use virtualenv *in* Docker. So, is it a virtual environment inside a virtual environment? I&#39;m confused as to how this would even work, so could someone please clarify?

What&#39;s the difference between Docker and Python virtualenv?

I am trying to install `apt-utils` on Docker because when I was just doing `apt-get update`, I was getting the error: `debconf: delaying package configuration, since apt-utils is not installed`. So I added a line to install `apt-utils` (along with `curl`):

    RUN apt-get update &amp;&amp; apt-get install -y apt-utils &amp;&amp; apt-get install -y curl

But, I am still getting that error leading me to believe that my command didn&#39;t work. Below is my output when I try to build the image.

    Step 5/12 : RUN apt-get update &amp;&amp; apt-get install -y apt-utils &amp;&amp; apt-get install -y curl
     ---&gt; Running in 6e6565ff01bd
    Get:1 http://security.debian.org jessie/updates InRelease [94.4 kB]
    Ign http://deb.debian.org jessie InRelease
    Get:2 http://deb.debian.org jessie-updates InRelease [145 kB]
    Get:3 http://deb.debian.org jessie Release.gpg [2420 B]
    Get:4 http://deb.debian.org jessie Release [148 kB]
    Get:5 http://security.debian.org jessie/updates/main amd64 Packages [624 kB]
    Get:6 http://deb.debian.org jessie-updates/main amd64 Packages [23.0 kB]
    Get:7 http://deb.debian.org jessie/main amd64 Packages [9098 kB]
    Fetched 10.1 MB in 6s (1541 kB/s)
    Reading package lists...
    Reading package lists...
    Building dependency tree...
    Reading state information...
    The following extra packages will be installed:
      libapt-inst1.5
    The following NEW packages will be installed:
      apt-utils libapt-inst1.5
    0 upgraded, 2 newly installed, 0 to remove and 24 not upgraded.
    Need to get 537 kB of archives.
    After this operation, 1333 kB of additional disk space will be used.
    Get:1 http://deb.debian.org/debian/ jessie/main libapt-inst1.5 amd64 1.0.9.8.4 [169 kB]
    Get:2 http://deb.debian.org/debian/ jessie/main apt-utils amd64 1.0.9.8.4 [368 kB]
    debconf: delaying package configuration, since apt-utils is not installed
    Fetched 537 kB in 0s (557 kB/s)
    Selecting previously unselected package libapt-inst1.5:amd64.
    (Reading database ... 21676 files and directories currently installed.)
    Preparing to unpack .../libapt-inst1.5_1.0.9.8.4_amd64.deb ...
    Unpacking libapt-inst1.5:amd64 (1.0.9.8.4) ...
    Selecting previously unselected package apt-utils.
    Preparing to unpack .../apt-utils_1.0.9.8.4_amd64.deb ...
    Unpacking apt-utils (1.0.9.8.4) ...
    Setting up libapt-inst1.5:amd64 (1.0.9.8.4) ...
    Setting up apt-utils (1.0.9.8.4) ...
    Processing triggers for libc-bin (2.19-18+deb8u10) ...
    Reading package lists...
    Building dependency tree...
    Reading state information...
    curl is already the newest version.
    0 upgraded, 0 newly installed, 0 to remove and 24 not upgraded.
    Removing intermediate container 6e6565ff01bd
     ---&gt; f65e29c6a6b9
    Step 6/12 : RUN curl -s https://packagecloud.io/install/repositories/github/git-lfs/script.deb.sh | bash
     ---&gt; Running in f5764ba56103
    Detected operating system as debian/8.
    Checking for curl...
    Detected curl...
    Checking for gpg...
    Detected gpg...
    Running apt-get update... done.
    Installing debian-archive-keyring which is needed for installing
    apt-transport-https on many Debian systems.
    Installing apt-transport-https... done.
    Installing /etc/apt/sources.list.d/github_git-lfs.list...done.
    Importing packagecloud gpg key... done.
    Running apt-get update... done.
    
    The repository is setup! You can now install packages.
    Removing intermediate container f5764ba56103
     ---&gt; a4e64687ab73

What is causing this and how can I fix it?

Docker: Having issues installing apt-utils

I&#39;m learning Docker. For many times I&#39;ve seen that `Dockerfile` has `WORKDIR` command:

    FROM node:latest
    RUN mkdir -p /usr/src/app
    WORKDIR /usr/src/app
    COPY package.json /usr/src/app/
    RUN npm install
    COPY . /usr/src/app
    EXPOSE 3000
    CMD [ “npm”, “start” ] 


Can&#39;t I just omit `WORKDIR` and `Copy` and just have my `Dockerfile` at the root of my project? What are the downsides of using this approach?

What is the point of WORKDIR on Dockerfile?

I have the problem with installing `node_modules` inside the Docker container and synchronize them with the host. My Docker&#39;s version is `18.03.1-ce, build 9ee9f40` and Docker Compose&#39;s version is ` 1.21.2, build a133471`. 

My `docker-compose.yml` looks like:

```yaml
# Frontend Container.
frontend:
  build: ./app/frontend
  volumes:
    - ./app/frontend:/usr/src/app
    - frontend-node-modules:/usr/src/app/node_modules
  ports:
    - 3000:3000
  environment:
    NODE_ENV: ${ENV}
  command: npm start

# Define all the external volumes.
volumes:
  frontend-node-modules: ~
```
My `Dockerfile`:

    # Set the base image.
    FROM node:10
    
    # Create and define the working directory.
    RUN mkdir /usr/src/app
    WORKDIR /usr/src/app
    
    # Install the application&#39;s dependencies.
    COPY package.json ./
    COPY package-lock.json ./
    RUN npm install

The trick with the external volume is described in a lot of blog posts and Stack Overflow answers. For example, [this one][1].

The application works great. The source code is synchronized. The hot reloading works great too.

The only problem that I have is that `node_modules` folder is empty on the host. Is it possible to synchronize the `node_modules` folder that is inside Docker container with the host?

I&#39;ve already read these answers:

 1. https://stackoverflow.com/questions/38425996/docker-compose-volume-on-node-modules-but-is-empty
 2. https://stackoverflow.com/questions/36245831/accessing-node-modules-after-npm-install-inside-docker

Unfortunately, they didn&#39;t help me a lot. I don&#39;t like [the first one][2], because I don&#39;t want to run `npm install` on my host because of the possible cross-platform issues (e.g. the host is Windows or Mac and the Docker container is Debian 8 or Ubuntu 16.04). [The second one][3] is not good for me too, because I&#39;d like to run `npm install` in my `Dockerfile` instead of running it after the Docker container is started.

Also, I&#39;ve found [this blog post][4]. The author tries to solve the same problem I am faced with. The problem is that `node_modules` won&#39;t be synchronized because we&#39;re just copying them from the Docker container to the host.

I&#39;d like my `node_modules` inside the Docker container to be synchronized with the host. Please, take into account that I want:

 - to install `node_modules` automatically instead of manually
 - to install `node_modules` inside the Docker container instead of the host
 - to have `node_modules` synchronized with the host (if I install some new package inside the Docker container, it should be synchronized with the host automatically without any manual actions)

I need to have `node_modules` on the host, because:

 - possibility to read the source code when I need
 - the IDE needs `node_modules` to be installed locally so that it could have access to the `devDependencies` such as `eslint` or `prettier`. I don&#39;t want to install these `devDependencies` globally.

Thanks in advance.

  [1]: https://stackoverflow.com/questions/30043872/docker-compose-node-modules-not-present-in-a-volume-after-npm-install-succeeds/32785014#32785014
  [2]: https://stackoverflow.com/a/43728476/4815056
  [3]: https://stackoverflow.com/a/36246223/4815056
  [4]: https://blog.sergeyev.info/docker-development-environment/

Content Type	Original Author	Original Content on Stackoverflow
Question	dingo_d	View Question on Stackoverflow
Solution 1 - Git	Alex Karshin	View Answer on Stackoverflow
Solution 2 - Git	emory	View Answer on Stackoverflow
Solution 3 - Git	Jairo Lozano	View Answer on Stackoverflow

git install fails in Dockerfile

Git Problem Overview

Git Solutions

Solution 1 - Git

Solution 2 - Git

Solution 3 - Git

What to do with Released persistent volume?

Breakpoints set but not yet bound in Visual Studio

Attributions