Closed ankurmalhotra07 closed 6 months ago
you've opened 3 different issues all related to the interaction with the EFS file system. Let's follow up on https://github.com/containers/podman/issues/22565 for now, as probably it is not an issue in Podman itself but in the network file system
Issue Description
When building an image stored in additional local storage (AWS EFS), podman shows the following error - `[1/4] STEP 1/7: FROM node:18-alpine AS build
time="2024-05-01T00:10:12Z" level=error msg="node:18-alpine exists in local storage but may be corrupted (remove the image to resolve the issue): layer not known"`
Steps to reproduce the issue
Steps to reproduce the issue
mount -t efs -o tls fs-123...:/ /var/lib/mycontainers
podman time podman --root /var/lib/mycontainers pull docker.io/node:18-alpine
Note: although podman pull was successful, a "corrupt image" error occurs when building the image using podman build.
Describe the results you received
`[1/4] STEP 1/7: FROM node:18-alpine AS build
time="2024-05-01T00:10:12Z" level=error msg="node:18-alpine exists in local storage but may be corrupted (remove the image to resolve the issue): layer not known"`
Describe the results you expected
podman successfully builds an image from the additional storage.
podman info output
Podman in a container
Yes
Privileged Or Rootless
Privileged
Upstream Latest Release
Yes
Additional environment details
Additional environment details
Fuse driver already installed - https://github.com/kuberenetes-learning-group/fuse-device-plugin/blob/master/README_EN.md
This is what storage.conf looks like:
[storage.options] additionalimagestores = ["/var/lib/mycontainers"]
[storage.options.overlay] ignore_chown_errors = "true" mount_program = "/usr/bin/fuse-overlayfs" mountopt = "nodev,fsync=0"