-
Notifications
You must be signed in to change notification settings - Fork 297
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
WCOW: build produces an unrunnable app image #800
Labels
Milestone
Comments
jromero
added
type/bug
Issue that reports an unexpected behaviour.
status/discussion-needed
Issue or PR that requires in-depth discussion.
os/windows
labels
Aug 12, 2020
micahyoung
pushed a commit
to micahyoung/buildpacks-samples
that referenced
this issue
Aug 13, 2020
- Add missing PATH env var to run image so that it gets properly set in app images - Can be removed once buildpacks/pack#800 is resolved Signed-off-by: Micah Young <[email protected]>
1 task
jromero
pushed a commit
that referenced
this issue
Aug 13, 2020
- Run images need to explicitly set `ENV PATH=C:\\windows...` to workaround differences in convetions for well-known Windows (mcr.microsoft.com/windows/nanoserver:1809) and Linux (alpine/bionic) base images - Windows base image configs set `Config.Env=null` - Linux base image configs set `Config.Env=["PATH=/usr/local/bin...",]` - Works-around #800 though a proper fix in lifecycle will be needed to allow unmodified stacks Signed-off-by: Micah Young <[email protected]>
dwillist
pushed a commit
to dwillist/pack
that referenced
this issue
Aug 14, 2020
- Run images need to explicitly set `ENV PATH=C:\\windows...` to workaround differences in convetions for well-known Windows (mcr.microsoft.com/windows/nanoserver:1809) and Linux (alpine/bionic) base images - Windows base image configs set `Config.Env=null` - Linux base image configs set `Config.Env=["PATH=/usr/local/bin...",]` - Works-around buildpacks#800 though a proper fix in lifecycle will be needed to allow unmodified stacks Signed-off-by: Micah Young <[email protected]>
micahyoung
pushed a commit
to micahyoung/buildpacks-samples
that referenced
this issue
Aug 20, 2020
- Add missing PATH env var to run image so that it gets properly set in app images - Can be removed once buildpacks/pack#800 is resolved Signed-off-by: Micah Young <[email protected]>
Related: buildpacks/rfcs#114 TLDR; won't fix |
jromero
added
status/blocked
Issue or PR that is blocked. See comments.
and removed
status/discussion-needed
Issue or PR that requires in-depth discussion.
labels
Sep 9, 2020
The eventual spec change, which would necessitate changes in lifecycle are here: buildpacks/spec#147 |
jromero
added
status/requires-rfc
Issue or PR that requires an RFC to be filed.
and removed
status/blocked
Issue or PR that is blocked. See comments.
type/bug
Issue that reports an unexpected behaviour.
labels
Sep 23, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
When building a Windows container using the latest version of lifecycle 0.9.0 (which uses platform API 0.4).
Reproduction
Steps
make build-windows-apps
from https://github.com/buildpacks/samples/pull/85/filesdocker run -it --rm sample-batch-script-app:nanoserver-1809
Current behavior
Expected behavior
Application runs as expected.
Environment
pack info
docker info
The text was updated successfully, but these errors were encountered: