This is how I finally achieve to bypass the problem in ansible:
First, I added a test to connect to the lxc container to check if sshd was functionnal or not.
This is because the playbook need to be idempotent.
If not, the ssh host keys would have been re-generated everytime we would have run...
Thanks for your answer.
The problem I see is that I really need to automate the container creation (in ansible/proxmoxer).
And ansible needs a working sshd to connect to the container...
Do you see a solution I could use to automate your solution ? Maybe "pct exec" ?
And do you think it will...
Hi everyone,
I can't make sshd working after creating a LXC container based on a centos6 template and using proxmox 6.2.
The error I got in the /var/log/messages of the container when I tried to ssh into is:
sshd: error: Could not load host key: /etc/ssh/ssh_host_rsa_key
sshd: error: Could not...
I have a strange message on the when starting (not migrating) the container:
Dec 6 18:01:18 hn-1-1-2 kernel: VE1001: no allowed mount options found for device 0:25
Anyone knows where it comes from ?
My mistake sorry.
Downgrading the kernel did not solve the problem.
And it is working fine on another cluster with same kernel version.
So it's not an upgrade problem, neither a kernel problem.
After upgrading kernel, it seems the NFS mounts are not working after live-migrating a CT.
The bug is very similar as this one (which is marked as solved in 042stab082_5): https://bugzilla.openvz.org/show_bug.cgi?id=2766 .
Migration seems ok but inside the VE, the NFS mount are not working...
Is this rather a Proxmox problem or an OpenVZ problem ?
It would be very usefull to have autofs working well in a CT (NFS is working like a charm so why not autofs ?).
Problem still exists in pve 3.1.
Also, there is a problem when stoping a CT using autofs inside (and running on the node local...
Does someone has a solution for a NFS server on proxmox that can be live-migrate easily ?
As it's still not possible in 3.1 to live-migrate a CT with nfsd inside, the only possibility is to shutdown the CT before migrating.
But it is really anoying because it has impacts on all the NFS...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.