Failures in my syslog

P

promoxer

Member
Apr 21, 2023
222
23
23
```
2025-05-13T08:39:28.022987+08:00 pve kernel: [224672.570816] overlayfs: failed to clone lowerpath
2025-05-13T08:39:31.040993+08:00 pve kernel: [224675.588274] overlayfs: failed to clone lowerpath
2025-05-13T08:39:33.857989+08:00 pve kernel: [224678.405149] overlayfs: failed to clone lowerpath
2025-05-13T08:39:38.081990+08:00 pve kernel: [224682.629884] overlayfs: failed to clone lowerpath
2025-05-13T08:39:39.734986+08:00 pve kernel: [224684.282168] overlayfs: failed to clone lowerpath
2025-05-13T08:39:45.867988+08:00 pve kernel: [224690.415398] overlayfs: failed to clone lowerpath
2025-05-13T08:39:46.098986+08:00 pve kernel: [224690.646447] overlayfs: failed to clone lowerpath
2025-05-13T08:39:48.148992+08:00 pve kernel: [224692.696094] overlayfs: failed to clone lowerpath
2025-05-13T08:39:50.236988+08:00 pve kernel: [224694.784246] overlayfs: failed to clone lowerpath
2025-05-13T08:39:51.793989+08:00 pve kernel: [224696.341586] overlayfs: failed to clone lowerpath
```

I'm getting alot of these in my `/var/log/syslog`, any ideas why?
 
Please provide some more information about your setup, esp. storage.
PVE does not use overlayfs by default for anything.

Have you maybe installed some OCI runtime like Docker onto the host directly and/or inside an LXC?
 
Then the above error messages stem from that. LXCs share the host kernel, so you will see kernel warnings/errors stemming from that in the host log.

Please note that running Docker in LXC is discouraged/not recommended, as it might lead to sudden and unpredictable problems, esp. with regard to networking (as Docker heavily interferes with host networking).
It is rather recommended to run it inside a VM, as also noted as such in our admin guide: https://pve.proxmox.com/pve-docs/pve-admin-guide.html#chapter_pct
 
promoxer said:
but that failure log has nothing to do with network right?
Click to expand...
No, in this case it's related to storage, i.e. something w.r.t. to the Docker images.
OCI runtimes like Docker use overlayfs to construct the final filesystem that containers see, by overlaying each OCI image layer with the next one.

You can look in the Docker daemon log itself, maybe there are some errors.
Best would probably to ask with the project you linked above, as this isn't really a supported configuration ..
 
You must log in or register to reply here.
Top Bottom