Closed flashpixx closed 2 years ago
@ashley-cui @baude PTAL
I am able to reproduce on my local machine as well:
# podman info
Client:
Version: 3.4.4
API Version: 3.4.4
Go Version: go1.17.3
Built: Wed Dec 8 13:41:11 2021
OS/Arch: darwin/arm64
Server:
Version: 3.4.2
API Version: 3.4.2
Go Version: go1.16.6
Built: Wed Dec 31 19:00:00 1969
OS/Arch: linux/arm64
# podman info --debug
host:
arch: arm64
buildahVersion: 1.23.1
cgroupControllers: []
cgroupManager: cgroupfs
cgroupVersion: v1
conmon:
package: 'conmon: /usr/libexec/podman/conmon'
path: /usr/libexec/podman/conmon
version: 'conmon version 2.0.30, commit: '
cpus: 2
distribution:
codename: focal
distribution: ubuntu
version: "20.04"
eventLogger: journald
hostname: podman
idMappings:
gidmap:
- container_id: 0
host_id: 1000
size: 1
- container_id: 1
host_id: 100000
size: 65536
uidmap:
- container_id: 0
host_id: 1000
size: 1
- container_id: 1
host_id: 100000
size: 65536
kernel: 5.4.0-91-generic
linkmode: dynamic
logDriver: journald
memFree: 2831626240
memTotal: 4114432000
ociRuntime:
name: crun
package: 'crun: /usr/bin/crun'
path: /usr/bin/crun
version: |-
crun version UNKNOWN
commit: ea1fe3938eefa14eb707f1d22adff4db670645d6
spec: 1.0.0
+SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +CRIU +YAJL
os: linux
remoteSocket:
exists: true
path: /run/user/1000/podman/podman.sock
security:
apparmorEnabled: false
capabilities: CAP_CHOWN,CAP_DAC_OVERRIDE,CAP_FOWNER,CAP_FSETID,CAP_KILL,CAP_NET_BIND_SERVICE,CAP_SETFCAP,CAP_SETGID,CAP_SETPCAP,CAP_SETUID,CAP_SYS_CHROOT
rootless: true
seccompEnabled: true
seccompProfilePath: /usr/share/containers/seccomp.json
selinuxEnabled: false
serviceIsRemote: true
slirp4netns:
executable: /usr/bin/slirp4netns
package: 'slirp4netns: /usr/bin/slirp4netns'
version: |-
slirp4netns version 1.1.8
commit: unknown
libslirp: 4.3.1-git
SLIRP_CONFIG_VERSION_MAX: 3
libseccomp: 2.4.3
swapFree: 0
swapTotal: 0
uptime: 30h 26m 48.7s (Approximately 1.25 days)
plugins:
log:
- k8s-file
- none
- journald
network:
- bridge
- macvlan
volume:
- local
registries:
search:
- docker.io
- quay.io
store:
configFile: /home/ubuntu/.config/containers/storage.conf
containerStore:
number: 0
paused: 0
running: 0
stopped: 0
graphDriverName: overlay
graphOptions:
overlay.mount_program:
Executable: /usr/bin/fuse-overlayfs
Package: 'fuse-overlayfs: /usr/bin/fuse-overlayfs'
Version: |-
fusermount3 version: 3.9.0
fuse-overlayfs: version 1.5
FUSE library version 3.9.0
using FUSE kernel interface version 7.31
graphRoot: /home/ubuntu/.local/share/containers/storage
graphStatus:
Backing Filesystem: extfs
Native Overlay Diff: "false"
Supports d_type: "true"
Using metacopy: "false"
imageStore:
number: 9
runRoot: /run/user/1000/containers
volumePath: /home/ubuntu/.local/share/containers/storage/volumes
version:
APIVersion: 3.4.2
Built: 0
BuiltTime: Wed Dec 31 19:00:00 1969
GitCommit: ""
GoVersion: go1.16.6
OsArch: linux/arm64
Version: 3.4.2
# brew info podman
podman: stable 3.4.4 (bottled), HEAD
Tool for managing OCI containers and pods
https://podman.io/
/opt/homebrew/Cellar/podman/3.4.4 (170 files, 41.0MB) *
Poured from bottle on 2021-12-14 at 13:20:42
From: https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/podman.rb
License: Apache-2.0
==> Dependencies
Build: go, go-md2man
Required: qemu
==> Options
--HEAD
Install HEAD version
==> Caveats
zsh completions have been installed to:
/opt/homebrew/share/zsh/site-functions
==> Analytics
install: 11,435 (30 days), 37,387 (90 days), 79,805 (365 days)
install-on-request: 11,436 (30 days), 37,393 (90 days), 79,798 (365 days)
build-error: 2 (30 days)
Apparent workaround (works for me at least); omit ./
from path.
podman build -t myservice:latest -f ./deploy/myservice.Dockerfile .
-> podman build -t myservice:latest -f deploy/myservice.Dockerfile .
A friendly reminder that this issue had no activity for 30 days.
Description
I’m using now podman 3.4.4 under OSX (Big Sur). I’m using podman-compose too, and I get an error, if my Dockerfile is located in a subdirectory (the name of the subdirectory will be duplicated twice in the path). I get the error
Steps to reproduce the issue:
Create a directory structure like
run
podman build -t myservice:latest -f ./deploy/myservice.Dockerfile .
See the minimal example and run the
run.sh
Describe the results you received:
The error comes up and the image building process breaks.
Describe the results you expected:
Working building process
Additional information you deem important (e.g. issue happens only occasionally):
It seems that this error exists only on OSX, because on Linux it works fine.
Output of
podman version
:Output of
podman info --debug
:Package info (
brew info podman
):Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/master/troubleshooting.md)
Yes