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

Cannot create and run any new container with pouch-cli. #652

Closed
g0194776 opened this issue Jan 26, 2018 · 14 comments
Closed

Cannot create and run any new container with pouch-cli. #652

g0194776 opened this issue Jan 26, 2018 · 14 comments
Assignees
Labels
kind/bug This is bug report for project

Comments

@g0194776
Copy link

Issue Description
Cannot create and run any new container with pouch-cli.

[root@xxx root]# pouch images
IMAGE ID       IMAGE NAME                         SIZE
1669a6aa7350   docker.io/library/busybox:latest   710.74 KB
76017ed0df70   docker.io/library/redis:alpine     9.71 MB

[root@xxx root]# pouch run 1669a6aa7350
Error: failed to run container: {"message":"image: 1669a6aa7350:latest: not found"}

[root@xxx root]# pouch run docker.io/library/busybox:latest
Error: failed to run container: {"message":"image: docker.io/library/busybox:latest: not found"}

Describe what happened:
After I've installed Pouch successfully, I was going to run a container as my first test.
Sadly, I could not run any containers up even though specified Image ID or Image name.

Describe what you expected to happen:
Successfully runs up a new container.

How to reproduce it (as minimally and precisely as possible):

  1. N/A
  2. N/A
  3. N/A

Anything else we need to know?:

Environment:

  • pouch version (use pouch version):
[root@xxx root]# pouch version
GitCommit:
GoVersion:       go1.9.1
KernelVersion:
Os:              linux
Version:         0.1.0
APIVersion:      1.24
Arch:            amd64
BuildTime:       2018-01-26T17:31:23.109824404+08:00
  • OS (e.g. from /etc/os-release):
[root@xxx root]# cat /etc/os-release
NAME="CentOS Linux"
VERSION="7 (Core)"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="7"
PRETTY_NAME="CentOS Linux 7 (Core)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:centos:centos:7"
HOME_URL="https://www.centos.org/"
BUG_REPORT_URL="https://bugs.centos.org/"
  • Kernel (e.g. uname -a):
    Linux xxx 3.10.0-693.11.6.el7.x86_64 add travis.yml for CI #1 SMP Thu Jan 4 01:06:37 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
  • Install tools: N/A
  • Others: N/A
@pouchrobot pouchrobot added the kind/bug This is bug report for project label Jan 26, 2018
@g0194776
Copy link
Author

@likakuli Please kindly follow this issue.

@allencloud
Copy link
Collaborator

Thanks for your feedback. @g0194776

[root@xxx root]# pouch run 1669a6aa7350
Error: failed to run container: {"message":"image: 1669a6aa7350:latest: not found"}

Actually we have not implemented using image ID to create a container. In 0.2.0, we will support this.

[root@xxx root]# pouch run docker.io/library/busybox:latest
Error: failed to run container: {"message":"image: docker.io/library/busybox:latest: not found"}

This error is not supposed. We will try to find the root cause. @Letty5411 @skoo87

@Letty5411
Copy link
Contributor

@g0194776 Could you also provide the daemon log?

@sunyuan3
Copy link
Contributor

I can't reproduce this issue in CentOS-7. Is this issue is reproducible in your environment?

log:

[root@iZj6c44nzox6sb97nzgmi0Z ~]# pouch images
IMAGE ID       IMAGE NAME                         SIZE
1669a6aa7350   docker.io/library/busybox:latest   710.74 KB
[root@iZj6c44nzox6sb97nzgmi0Z ~]# pouch run -ti docker.io/library/busybox:latest sh
/ #

@g0194776
Copy link
Author

@sunyuan3
Yes, I can reproduce this issue each time by performing the command of pouch run.

@Letty5411
I'll provide deamon logs ASAP after this weekend.

@sunyuan3
Copy link
Contributor

@g0194776 You can get daemon log by "journalctl" command.
Could you please provide your centos iso link?

@g0194776
Copy link
Author

@sunyuan3

I got no any recent logs (EMPTY) by performing "journalctl -u pouch" after I performed "pouch run docker.io/library/busybox" command.

Ours CentOS-7 was initialized & installed by Hypver-v OS images.

@sunyuan3
Copy link
Contributor

hi @g0194776 , Please stop pouch service and start pouch daemon in the following command manually.

pouchd

Then reproduce your defect in other terminal.

@g0194776
Copy link
Author

@sunyuan3

[root@xxx ~]# pouchd
INFO[0000] starting containerd                           module=containerd revision=89623f28b87a6004d4b785663257362d1658a729 version=v1.0.0
INFO[0000] setting subreaper...                          module=containerd
INFO[0000] loading plugin "io.containerd.content.v1.content"...  module=containerd type=io.containerd.content.v1
INFO[0000] loading plugin "io.containerd.snapshotter.v1.btrfs"...  module=containerd type=io.containerd.snapshotter.v1
WARN[0000] failed to load plugin io.containerd.snapshotter.v1.btrfs  error="path /var/lib/pouch/containerd/root/io.containerd.snapshotter.v1.btrfs must be a btrfs filesystem to be used with the btrfs snapshotter" module=containerd
INFO[0000] loading plugin "io.containerd.snapshotter.v1.overlayfs"...  module=containerd type=io.containerd.snapshotter.v1
WARN[0000] failed to load plugin io.containerd.snapshotter.v1.overlayfs  error="/var/lib/pouch/containerd/root/io.containerd.snapshotter.v1.overlayfs does not support d_type. If the backing filesystem is xfs, please reformat with ftype=1 to enable d_type support" module=containerd
INFO[0000] loading plugin "io.containerd.metadata.v1.bolt"...  module=containerd type=io.containerd.metadata.v1
WARN[0000] could not use snapshotter btrfs in metadata plugin  error="path /var/lib/pouch/containerd/root/io.containerd.snapshotter.v1.btrfs must be a btrfs filesystem to be used with the btrfs snapshotter" module="containerd/io.containerd.metadata.v1.bolt"
WARN[0000] could not use snapshotter overlayfs in metadata plugin  error="/var/lib/pouch/containerd/root/io.containerd.snapshotter.v1.overlayfs does not support d_type. If the backing filesystem is xfs, please reformat with ftype=1 to enable d_type support" module="containerd/io.containerd.metadata.v1.bolt"
INFO[0000] loading plugin "io.containerd.differ.v1.walking"...  module=containerd type=io.containerd.differ.v1
INFO[0000] loading plugin "io.containerd.gc.v1.scheduler"...  module=containerd type=io.containerd.gc.v1
INFO[0000] loading plugin "io.containerd.grpc.v1.containers"...  module=containerd type=io.containerd.grpc.v1
INFO[0000] loading plugin "io.containerd.grpc.v1.content"...  module=containerd type=io.containerd.grpc.v1
INFO[0000] loading plugin "io.containerd.grpc.v1.diff"...  module=containerd type=io.containerd.grpc.v1
INFO[0000] loading plugin "io.containerd.grpc.v1.events"...  module=containerd type=io.containerd.grpc.v1
INFO[0000] loading plugin "io.containerd.grpc.v1.healthcheck"...  module=containerd type=io.containerd.grpc.v1
INFO[0000] loading plugin "io.containerd.grpc.v1.images"...  module=containerd type=io.containerd.grpc.v1
INFO[0000] loading plugin "io.containerd.grpc.v1.leases"...  module=containerd type=io.containerd.grpc.v1
INFO[0000] loading plugin "io.containerd.grpc.v1.namespaces"...  module=containerd type=io.containerd.grpc.v1
INFO[0000] loading plugin "io.containerd.grpc.v1.snapshots"...  module=containerd type=io.containerd.grpc.v1
INFO[0000] loading plugin "io.containerd.monitor.v1.cgroups"...  module=containerd type=io.containerd.monitor.v1
INFO[0000] loading plugin "io.containerd.runtime.v1.linux"...  module=containerd type=io.containerd.runtime.v1
INFO[0000] loading plugin "io.containerd.grpc.v1.tasks"...  module=containerd type=io.containerd.grpc.v1
INFO[0000] loading plugin "io.containerd.grpc.v1.version"...  module=containerd type=io.containerd.grpc.v1
INFO[0000] loading plugin "io.containerd.grpc.v1.introspection"...  module=containerd type=io.containerd.grpc.v1
INFO[0000] serving...                                    address="/run/containerd/debug.sock" module="containerd/debug"
INFO[0000] serving...                                    address="/var/run/containerd.sock" module="containerd/grpc"
INFO[0000] containerd successfully booted in 0.003491s   module=containerd
INFO[2018-01-30 11:08:24.365698767] success to create containerd's client, connect to: /var/run/containerd.sock
INFO[0000] Firewalld running: false
INFO[2018-01-30 11:08:24.501749439] start to listen to: unix:///var/run/pouchd.sock
INFO[2018-01-30 11:08:35.050318730] Calling POST /containers/create, client @
INFO[2018-01-30 11:08:41.807995249] Calling POST /containers/create, client @
INFO[2018-01-30 11:08:42.672779478] Calling POST /containers/create, client @
INFO[2018-01-30 11:08:43.168108869] Calling POST /containers/create, client @

@sunyuan3
Copy link
Contributor

ping @allencloud @skoo87 Could you please check with the issue?

WARN[0000] failed to load plugin io.containerd.snapshotter.v1.btrfs  error="path /var/lib/pouch/containerd/root/io.containerd.snapshotter.v1.btrfs must be a btrfs filesystem to be used with the btrfs snapshotter" module=containerd
WARN[0000] failed to load plugin io.containerd.snapshotter.v1.overlayfs  error="/var/lib/pouch/containerd/root/io.containerd.snapshotter.v1.overlayfs does not support d_type. If the backing filesystem is xfs, please reformat with ftype=1 to enable d_type support" module=containerd

@g0194776
Copy link
Author

g0194776 commented Feb 5, 2018

@sunyuan3

Did I miss some updates here?
What's the newest status of my issue?

thanks a lot.

@sunyuan3
Copy link
Contributor

sunyuan3 commented Feb 5, 2018

@g0194776 Please send your wechat account to my email yile.sy@alibaba-inc.com.
We need to discuss for details.

@g0194776
Copy link
Author

g0194776 commented Feb 5, 2018

@sunyuan3 I've sent it out.

@sunyuan3
Copy link
Contributor

sunyuan3 commented Feb 6, 2018

@g0194776 I have added you in wechat.

@g0194776 g0194776 closed this as completed Feb 6, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug This is bug report for project
Projects
None yet
Development

No branches or pull requests

5 participants