Skip to content

Permission denied when accessing .docker-root/overlay2 #10108

Closed
@sagor999

Description

@sagor999

Bug description

I see a lot (40k in last 3 hours) errors like this in SaaS:

jsonPayload: {
@type: "type.googleapis.com/google.devtools.clouderrorreporting.v1beta1.ReportedErrorEvent"
error: "permission denied"
gid: 33333
level: "warning"
message: "cannot chown"
path: ".docker-root/overlay2/205df79f676c4bbc3e8af627dc2a78228e55f494d7b21c5725fcaeb808e285cb/diff/home/node/parse-server/"
uid: 33333

Link to logs: https://cloudlogging.app.goo.gl/mZg3N1J2w58wm7fLA

This might be related to an issue customer is having as well:
https://app.frontapp.com/inboxes/teammates/9932874/inbox/open/41825492426

Potentially related issue: #9263

Would like to understand why we are getting those errors and what is the impact.

Steps to reproduce

One potential repro case:
This seems to do with running docker-compose pull and docker-compose build in init task.

Workspace affected

tracthq-tractweb-xtjbxw26gqh

Expected behavior

We shouldn't be getting permission denied errors when accessing .docker-root I think.

Example repository

No response

Anything else?

No response

Metadata

Metadata

Assignees

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions