Comments (3)
hey @dmikusa-pivotal it looks like this problem occurs when you rebuild the same app using two different builders with different PACK_USER_ID
and PACK_USER_GID
values.
If you build with a builder based on the io.buildpacks.stacks.bionic
stack, files in the cache volume will be owned by pack. If you subsequently build with a cflinuxfs3
builder, you will see this permission error.
We can fix this in pack
by ensuring we change the ownership of all files in the cache volume before detecting. However this problem situation should be unlikely to arise after we play buildpacks/roadmap#28.
For now, if you remove the cache volume between builds or build from different paths in these two cases, you can work around the issue.
from lifecycle.
Excellent! I'll give that a try. Thanks!
from lifecycle.
Following up. That did, in fact, resolve the issue I was seeing. I just missed those cache volumes.
Running docker volume ls
shows the volumes and docker volume prune
seemed to clean them up.
Thanks!
from lifecycle.
Related Issues (20)
- Documenting known issue: `failed to get platform API version` HOT 1
- CVE(s) found in v0.18.4 HOT 2
- Run image extension does not install RPMs that are already installed in the builder HOT 5
- Make extensions not experimental for Platform 0.13 and above HOT 7
- Upgrade lifecycle to go1.21.7 HOT 1
- When using extensions, if the last layer in the run image is duplicated, then the process fail with an error HOT 4
- Add support for ppc64le
- `CNB_TARGET_` environment variables are not set when expected HOT 1
- Upgrade lifecycle to go1.21.8 HOT 1
- CVE(s) found in v0.19.0 HOT 1
- lifecycle 0.19.0 doesn't support Buildpack API 0.11 contrary to API support matrix HOT 1
- `CNB_TARGET_DISTRO_NAME` and `CNB_TARGET_DISTRO_VERSION` not set correctly in buildpack env HOT 3
- Target distro name/version not derived from `/etc/os-release` when Docker labels aren't set HOT 3
- `[[targets.distros]]` in `buildpack.toml` is ignored if the run image distro name/version isn't available HOT 3
- CVE(s) found in v0.19.3 HOT 1
- AppDir should be marked as readonly in export.go HOT 6
- Lifecycle fails to build on a stack other than bionic HOT 2
- Source file mtimes are always set to Jan 1, 1980 HOT 5
- Upgrade lifecycle to go1.22.4 HOT 1
- UX: Call out ordering of buildpacks when failing detection HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from lifecycle.