Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed to run 'make run-docker-py-tests' #9229

Closed
chuanchang opened this issue Feb 4, 2021 · 9 comments
Closed

Failed to run 'make run-docker-py-tests' #9229

chuanchang opened this issue Feb 4, 2021 · 9 comments
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug. kind/feature Categorizes issue or PR as related to a new feature. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. stale-issue

Comments

@chuanchang
Copy link
Contributor

Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)

/kind bug

/kind feature

Description

Steps to reproduce the issue:

  1. make all

  2. make run-docker-py-tests and select an image

Describe the results you received:

[root@kvm-04-guest06 podman]# git rev-parse HEAD
4e1bcf30f3a519490f58d66bc0aef16676f61ae8

[root@kvm-04-guest06 podman]# make run-docker-py-tests
./bin/podman run --rm --security-opt label=disable --privileged -v /tmp/tmp.5iQOaMj5lu:/testLogs --net=host -e DOCKER_HOST=tcp://localhost:8080  sh -c "pytest  "
✔ registry.access.redhat.com/sh:latest
Trying to pull registry.access.redhat.com/sh:latest...
  name unknown: Repo not found
Error: Error initializing source docker://registry.access.redhat.com/sh:latest: Error reading manifest latest in registry.access.redhat.com/sh: name unknown: Repo not found
make: *** [Makefile:258: run-docker-py-tests] Error 125

[root@kvm-04-guest06 podman]# ./bin/podman login registry.redhat.io
Username: XXX
Password:
Login Succeeded!

[root@kvm-04-guest06 podman]# make run-docker-py-tests
./bin/podman run --rm --security-opt label=disable --privileged -v /tmp/tmp.zEhftbfat3:/testLogs --net=host -e DOCKER_HOST=tcp://localhost:8080  sh -c "pytest  "
✔ registry.redhat.io/sh:latest
Trying to pull registry.redhat.io/sh:latest...
WARN[0004] failed, retrying in 1s ... (1/3). Error: Error initializing source docker://registry.redhat.io/sh:latest: Error reading manifest latest in registry.redhat.io/sh: unknown: Not Found
WARN[0009] failed, retrying in 2s ... (2/3). Error: Error initializing source docker://registry.redhat.io/sh:latest: Error reading manifest latest in registry.redhat.io/sh: unknown: Not Found
WARN[0016] failed, retrying in 4s ... (3/3). Error: Error initializing source docker://registry.redhat.io/sh:latest: Error reading manifest latest in registry.redhat.io/sh: unknown: Not Found
^Cmake: *** [Makefile:258: run-docker-py-tests] Error 1

[root@kvm-04-guest06 podman]# make run-docker-py-tests
./bin/podman run --rm --security-opt label=disable --privileged -v /tmp/tmp.QsxZn2UjTC:/testLogs --net=host -e DOCKER_HOST=tcp://localhost:8080  sh -c "pytest  "
✔ docker.io/library/sh:latest
Trying to pull docker.io/library/sh:latest...
  denied: requested access to the resource is denied
Error: Error initializing source docker://sh:latest: Error reading manifest latest in docker.io/library/sh: errors:
denied: requested access to the resource is denied
unauthorized: authentication required

make: *** [Makefile:258: run-docker-py-tests] Error 125

Describe the results you expected:
fix image path

Additional information you deem important (e.g. issue happens only occasionally):

Output of podman version:

[root@kvm-04-guest06 podman]# ./bin/podman version
Version:      3.0.0-dev
API Version:  3.0.0
Go Version:   go1.15.7
Git Commit:   4e1bcf30f3a519490f58d66bc0aef16676f61ae8
Built:        Thu Feb  4 05:04:47 2021
OS/Arch:      linux/amd64

Output of podman info --debug:

[root@kvm-04-guest06 podman]# ./bin/podman version
Version:      3.0.0-dev
API Version:  3.0.0
Go Version:   go1.15.7
Git Commit:   4e1bcf30f3a519490f58d66bc0aef16676f61ae8
Built:        Thu Feb  4 05:04:47 2021
OS/Arch:      linux/amd64
[root@kvm-04-guest06 podman]# ./bin/podman info --debug
host:
  arch: amd64
  buildahVersion: 1.19.3
  cgroupManager: systemd
  cgroupVersion: v1
  conmon:
    package: conmon-2.0.25-1.module+el8.4.0+9742+44abad1f.x86_64
    path: /usr/bin/conmon
    version: 'conmon version 2.0.25, commit: 5b85dab80c329034b2d00187c1f48663db850ac0'
  cpus: 1
  distribution:
    distribution: '"rhel"'
    version: "8.4"
  eventLogger: file
  hostname: kvm-04-guest06.hv2.lab.eng.bos.redhat.com
  idMappings:
    gidmap: null
    uidmap: null
  kernel: 4.18.0-280.el8.x86_64
  linkmode: dynamic
  memFree: 1794441216
  memTotal: 3917811712
  ociRuntime:
    name: crun
    package: crun-0.17-1.module+el8.4.0+9742+44abad1f.x86_64
    path: /usr/bin/crun
    version: |-
      crun version 0.17
      commit: 0e9229ae34caaebcb86f1fde18de3acaf18c6d9a
      spec: 1.0.0
      +SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +YAJL
  os: linux
  remoteSocket:
    exists: true
    path: /run/podman/podman.sock
  security:
    apparmorEnabled: false
    capabilities: CAP_NET_RAW,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: false
    seccompEnabled: true
    selinuxEnabled: true
  slirp4netns:
    executable: ""
    package: ""
    version: ""
  swapFree: 4257214464
  swapTotal: 4257214464
  uptime: 16h 15m 42.51s (Approximately 0.67 days)
registries:
  registry-proxy.engineering.redhat.com:
    Blocked: false
    Insecure: true
    Location: registry-proxy.engineering.redhat.com
    MirrorByDigestOnly: false
    Mirrors: []
    Prefix: registry-proxy.engineering.redhat.com
  search:
  - registry.access.redhat.com
  - registry.redhat.io
  - docker.io
store:
  configFile: /etc/containers/storage.conf
  containerStore:
    number: 0
    paused: 0
    running: 0
    stopped: 0
  graphDriverName: overlay
  graphOptions:
    overlay.mountopt: nodev,metacopy=on
  graphRoot: /var/lib/containers/storage
  graphStatus:
    Backing Filesystem: xfs
    Native Overlay Diff: "false"
    Supports d_type: "true"
    Using metacopy: "true"
  imageStore:
    number: 15
  runRoot: /run/containers/storage
  volumePath: /var/lib/containers/storage/volumes
version:
  APIVersion: 3.0.0
  Built: 1612433087
  BuiltTime: Thu Feb  4 05:04:47 2021
  GitCommit: 4e1bcf30f3a519490f58d66bc0aef16676f61ae8
  GoVersion: go1.15.7
  OsArch: linux/amd64
  Version: 3.0.0-dev

Package info (e.g. output of rpm -q podman or apt list podman):

[root@kvm-04-guest06 podman]# git rev-parse HEAD
4e1bcf30f3a519490f58d66bc0aef16676f61ae8

Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide?

Yes/No

Additional environment details (AWS, VirtualBox, physical, etc.):

[root@kvm-04-guest06 podman]# cat /etc/redhat-release
Red Hat Enterprise Linux release 8.4 Beta (Ootpa)
@openshift-ci-robot openshift-ci-robot added kind/bug Categorizes issue or PR as related to a bug. kind/feature Categorizes issue or PR as related to a new feature. labels Feb 4, 2021
@edsantiago edsantiago assigned jwhonce and unassigned edsantiago Feb 8, 2021
@edsantiago
Copy link
Member

The run-docker-py-tests target requires setting $DOCKERPY_IMAGES and $DOCKERPY_TEST environment variables. There is no indication of what those should be.

The run-docker-py-tests target was added in #4832. Although that PR is owned by @baude, that particular commit (d924494) was by @jwhonce. It looks like those environment variables are part of his local setup, but (according to git log -S) were never made part of the source tree nor documented anywhere.

I have assigned this to @jwhonce. Jhon: if this is a target that should be used by others, could you please submit a PR documenting those envariables and perhaps setting them to a default value? If this target should not be used by others, could you please remove it? Thanks.

@github-actions
Copy link

A friendly reminder that this issue had no activity for 30 days.

@vrothberg
Copy link
Member

Ping @jwhonce

@github-actions
Copy link

A friendly reminder that this issue had no activity for 30 days.

@rhatdan
Copy link
Member

rhatdan commented Jul 11, 2021

Still waiting for @jwhonce comments.

@github-actions
Copy link

A friendly reminder that this issue had no activity for 30 days.

@rhatdan
Copy link
Member

rhatdan commented Aug 11, 2021

I believe @jwhonce is working on this now.

@github-actions
Copy link

A friendly reminder that this issue had no activity for 30 days.

@vrothberg
Copy link
Member

I cannot reproduce (anymore), so I am closing.

@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 21, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 21, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/bug Categorizes issue or PR as related to a bug. kind/feature Categorizes issue or PR as related to a new feature. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. stale-issue
Projects
None yet
Development

No branches or pull requests

6 participants