Hello,
I am working on using OpenAFS client in LXC containers.

I managed to have OpenAFS client work in one LXC container. I went with
loading the kernel module on host, and installing OpenAFS client on
container.
Here is detailed info on what I did:
- I installed OpenAFS kernel module on host (CentOS 7.1) / kmod-openafs
v1.6.9
- I create a CentOS 7.1 LXC container,
- and install OpenAFS client in this container
(openafs-client openafs-krb5 krb5-workstation)
- systemd script to start openafs-client does not fit because it tries to
load the kernel module, which is not possible by default in my container.
So I start by myself afsd service (/usr/vice/etc/afsd)
- It's working fine, and I can access AFS shares


I have 2 problems:

1) When I terminate my container, and create a new one, and do the exact
same procedure, starting afsd gets stuck when trying to fork background
processes. I can see that these processes go into zombie state.

2) When I keep my container, and create a second one along, and do the same
installation. Starting afsd fails with the following error:
afsd: Error calling AFSOP_CACHEINODE: not configured
I have seen that it comes when trying to run multiple openafs client on the
same machine. Which is what I am trying to do, but I was expecting that it
would work in containers, because afsd is a userspace process, and
containers are namespaced.


Bertrand

Reply via email to