Search results

Just tested and confirmed that the container OS doesn't seem to be a factor, I had been using Debian 9.1-9.3 in the containers but spun up separate CentOS and Arch Linux containers, once one is started, the other cannot start and returns the same result when started with the debug log level...

Have an odd issue on a non-production server i've been running for a few months. Starting/restarting a container (ID 101 for example) while any other container is active will cause the 2nd CT's network pair to be generated as veth101i0@vethXXYYZZ rather than veth101i0@ifX as it usually does, and...