Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error when creating new container from image generated by committing the prod container #468

Open
PTC-JoshuaMatthews opened this issue Sep 29, 2017 · 1 comment

Comments

@PTC-JoshuaMatthews
Copy link

I'm submitting a ... (check one with "x")

[X] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here, instead see use [gitter](https://gitter.im/mgechev/angular2-seed) or [stackoverflow](https://stackoverflow.com/questions/tagged/angular2)

Current behavior

Run prod build script to generate the angular-seed-nginx-prod container. docker commit that container to a new image. Attempt to docker up the new image.

Expected behavior

New container should be created with angular site running on localhost:5555
Minimal reproduction of the problem with instructions

Instead get error

Error response from daemon: cannot mount volume over existing file, file exists /var/lib/docker/overlay2/2b595d7cbdeaba17e5f0ad17011c28819bedac789379f4fb2829c53f5d0323d0/merged/etc/nginx/conf.d/angular-seed.template

What is the motivation / use case for changing the behavior?

Need to deploy the prod built application to a registry, image needs to useable for creating a container
Please tell us about your environment:

OSX

  • Angular Seed Version: aaaaf75
  • Node: node --version =
@kalaGN
Copy link

kalaGN commented Oct 16, 2019

i have the same question!,i can't how to fix it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants