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

cat: /proc/meminfo: Transport endpoint is not connected #2805

Closed
ruguodangshi opened this issue Apr 19, 2019 · 1 comment
Closed

cat: /proc/meminfo: Transport endpoint is not connected #2805

ruguodangshi opened this issue Apr 19, 2019 · 1 comment
Assignees
Labels
kind/bug This is bug report for project lxcfs related to lxcfs

Comments

@ruguodangshi
Copy link

ruguodangshi commented Apr 19, 2019

Ⅰ. Issue Description

when I run "cat /proc/meminfo" in a pouch container after I run “systemctl restart pouch-lxcfs ” on the host machine,return the result “cat: /proc/meminfo: Transport endpoint is not connected”.

Ⅱ. Describe what happened

Ⅲ. Describe what you expected to happen

Should return the content of /proc/meminfo in the container normally

Ⅳ. How to reproduce it (as minimally and precisely as possible)

1.Start a pouch container
pouch run -it --enableLxcfs=true -m 512m --cpuset-cpus=5 registry.hub.docker.com/library/centos:6 bash
2.Restart lxcfs
On the host machine,run "systemctl restart pouch-lxcfs "
3.View error message
in the pouch container,run “ cat /proc/meminfo ”

Ⅴ. Anything else we need to know?

1、cat /usr/lib/systemd/system/pouch-lxcfs.service
[Unit]
Description=FUSE filesystem for LXC
ConditionVirtualization=!container
Before=lxc.service
Documentation=man:lxcfs(1)
[Service]
ExecStart=/usr/local/bin/pouch-lxcfs /var/lib/pouch-lxcfs/
KillMode=process
Restart=on-failure
ExecStopPost=-/usr/bin/fusermount -u /var/lib/pouch-lxcfs
Delegate=yes
ExecStartPost=pouch remount-lxcfs
[Install]
WantedBy=multi-user.target
2、cat /usr/lib/systemd/system/pouch.service
[Unit]
Description=pouch

[Service]
ExecStart=/usr/local/bin/pouchd --enable-lxcfs --lxcfs /usr/local/bin/pouch-lxcfs --lxcfs-home /var/lib/pouch-lxcfs/
ExecReload=/bin/kill -HUP $MAINPID
Type=notify

LimitNOFILE=infinity
LimitNPROC=infinity
LimitCORE=infinity

TimeoutStartSec=0
Delegate=yes

KillMode=process

Restart=on-failure
StartLimitBurst=3
StartLimitInterval=60s

[Install]
WantedBy=multi-user.target

Ⅵ. Environment:

  • pouch version (use pouch version):
    APIVersion: 1.24
    Arch: amd64
    BuildTime: 2019-02-14T01:54:05+00:00
    GitCommit: 1.2.0
    GoVersion: go1.10.4
    KernelVersion: 4.9.148-
    Os: linux
    Version: 1.2.0
  • OS (e.g. from /etc/os-release):
    CentOS Linux release 7.4.1708 (Core)
  • Kernel (e.g. uname -a):
    4.9.148
  • Install tools:
  • Others:
@allencloud allencloud added lxcfs related to lxcfs kind/bug This is bug report for project labels Apr 20, 2019
@ruguodangshi
Copy link
Author

I found:

// runRemountLxcfs is the entry of remountLxcfsCommand command.
func (p *RemountLxcfsCommand) runRemountLxcfs(args []string) error {
	// TODO: get containers which enable lxcfs, and exec remount in them
	return nil
}

in remount_lxcfs.go.so,this feature has not been implemented yet?

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 lxcfs related to lxcfs
Projects
None yet
Development

No branches or pull requests

4 participants