I've been having some strange problems with my Proxmox installation.
First, I've found that when I've done an `apt update && apt upgrade` - after it's been running for a while - I've seen out of storage errors:
Job for pve-ha-lrm.service failed because a timeout was exceeded.
See "systemctl...
Interesting, I clearly have not understood the intention here. So does `docker-machine` run on a workstation your driver facilitates allocation of a docker instance via `docker-machine` on a Proxmox server? I'm still getting some crossed wires... Could you elaborate on the process more fully...
@LnxBil would you mind giving some more explicit instructions on installation? For example, putting it within $PATH would essentially indicate, on Proxmox, sticking the downloaded bin to any of the defaults: "/root/bin:/usr/local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"...
For some of us who run Proxmox for dev envs and small offices, can we get a way to set this permanently such that a quorum can always be 1 in a 2 server config? Even having a simple web interface option that we could set would be helpful. It would have saved me over an hour of headache today if...
@LnxBil so the reason I foresee using Docker in LXC is simply for testing/staging purposes on isolated instances that have no security risks.
However, would it be possible to have a "Create DC" at the top for a Docker container as well in Proxmox via your driver implementation? I could see that...
I did enable it this via the options method:
However I still get the same AppArmor issue:
/usr/bin/docker: Error response from daemon: Could not check if docker-default AppArmor profile was loaded: open /sys/kernel/security/apparmor/profiles: permission denied.
Thanks for the concern: No, this is on an isolated LAN with no security risk whatsoever for development/staging/testing only purposes. I'm still hitting a wall here and would like to know how to get past this open /sys/kernel/security/apparmor/profiles: permission denied issue.
These are excellent instructions @LnxBil, but I'm hitting an issue still - could you take a look and advise accordingly?:
/usr/bin/docker: Error response from daemon: Could not check if docker-default AppArmor profile was loaded: open /sys/kernel/security/apparmor/profiles: permission denied...
To document my steps at getting Docker with Discourse working further, I edited:
/etc/pve/nodes/nodename/lxc
to contain:
lxc.apparmor.profile: unconfined
lxc.cgroup.devices.allow: a
lxc.cap.drop:
I then edited `nano /etc/modules` to contain:
aufs
overlay
I rebooted to verify that these...
It turns out that I did hit a wall running Docker within an LXC container and this appears to be the solution to :
https://forum.proxmox.com/threads/container-linux-in-a-kvm.43136/#post-207264
Being able to use Dockerized apps within LXC containers is a pretty important function that we need. Just wanted to mention that we'd also like to see this brought into being a first class and supported citizen of the Proxmox environment.
So this got me to the next point of my question regarding Docker. It turns out that Discourse will not work with the `vfs` storage driver. Is there a way to use aufs or overlay2 instead with Proxmox?
In the past `halt` has effectively shut down the Proxmox VM entirely such that I can restart it again.
`Poweroff` is hanging the system. It appears as though it's not initiating the actual shutdown or not completing it entirely. Yes, there is something wrong here and this is the 3rd instance...
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.