-
Notifications
You must be signed in to change notification settings - Fork 50
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
start.sh no such file or directory #8
Comments
can't see any reason why this should have happened. maybe the mkdir line needs a pre slash and the step 11 needs the slash removing off the end of the bootstrap bit.
paul
…---- On Mon, 29 Jul 2019 09:45:11 +0000 [email protected] wrote ----
Running this of as is I get following error
docker-compose up
Step 11/14 : ADD start.sh /bootstrap/
ERROR: Service 'myservice' failed to build: ADD failed: stat /mnt/sda1/var/lib/docker/tmp/docker-builder574939908/start.sh: no such file or directory
PS C:\CustomerDockers\ulsmith\app>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
nope that didn't help, but thanks for the suggestion |
strange. can't say I have ever had this issue or heard it before. have you got any other info that might even slightly point me in a direction that could help? Details about how and what your deploying on, docker version, docker compose version of using etc.
paul
…---- On Mon, 29 Jul 2019 15:24:45 +0000 [email protected] wrote ----
nope that didn't help, but thanks for the suggestion
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Running this of as is I get following error
docker-compose up
Step 11/14 : ADD start.sh /bootstrap/
ERROR: Service 'myservice' failed to build: ADD failed: stat /mnt/sda1/var/lib/docker/tmp/docker-builder574939908/start.sh: no such file or directory
PS C:\CustomerDockers\ulsmith\app>
The text was updated successfully, but these errors were encountered: