Oh and .clone()
Oh and .clone()
They’re “complaining” about unique qualities of their art being used, without consent, to create new things which ultimately de-value their original art.
It’s a debate to be had, I’m not clearly in favour of either argument here, but it’s quite obvious what they’re upset with.
Don’t oversimplify though, remember you need to put lightning into it first!
Not sure whether this was definitely the issue, but interesting nonetheless.
FBI: nice save…
With the specific exception of podman compose I completely agree. I haven’t tested it for a while but podman compose has had issues with compose file syntax in my experience. Especially with network configs.
However, I have been using “docker-compose” with podman’s docker compatible socket implementation when necessary, with great success
It depends how wireguard is implemented.
The container may be running wireguard in userspace, instead of the OS’s kernel implementation.
Asking for info: What’s you specific concern regarding this information? Is it that data is accessible in the USA, you don’t trust the company?