LXD VS Artifactory

LXD Reviews

Artifactory Reviews

LXD mentions (9)

• Canonical re-licenses LXD under AGPLv3, slaps a CLA on top

  Linux containers project. Foreshadowing of this move at https://linuxcontainers.org/lxd/. - Source: Hacker News / 5 months ago

• LXD is now under Canonical

  The expected changes are: - https://github.com/lxc/lxd will now become https://github.com/canonical/lxd - https://linuxcontainers.org/lxd will disappear and be replaced with a mention directing users to https://ubuntu.com/lxd - The LXD YouTube channel will be handed over to the Canonical team - The LXD section on the LinuxContainers community forum will slowly Be sunset in favor of the Ubuntu Discourse forum... Source: 11 months ago

• LXC images download

  Hello community, It seems LXC images for arm7l/armhf are no longer available, not from the official Turris mirror nor from LinuxContainers.org (https://linuxcontainers.org/lxd/). Any solution or alternative for people like me heavily relying on the Turris Omnia to run LXC containers? Thanks. Source: 11 months ago

• Bought a mini pc to run Proxmox bare metal but the storage is emmc which PM hates. What should I run instead to self host containers and vms?

  Any distribution stable enough and LXD https://linuxcontainers.org/lxd/ for containers and VMs. Source: about 1 year ago

• Rancher K3s: Kubernetes on Proxmox Containers

  This has been really stable, and has worked pretty well for me. I deploy the applications to a set of LXD containers (read: lightweight Linux VMs) on Proxmox, a free and open-source hypervisor with an excellent management interface. - Source: dev.to / about 2 years ago

Artifactory mentions (20)

• Where to store executables shared by a team/project

  I kind of hate it, but Artifactory seems popular at companies: https://jfrog.com/artifactory/. Source: 11 months ago

• Adding Virtual Environments to Git Repo

  When not providing all dependencies yourself, you might suffer from people deleting the packages you depend on (IMHO a very rare scenario). If it is really that critical (hint: usually it isn't), create a local mirror of Pypi (full or only the packages you need). Devpi, Artifactory, etc. Can do that or you just dump the necessary files into Cloud storage, so you have a backup. Source: about 1 year ago

• Authenticated Docker Hub image pulls in Kubernetes

  Operate a pull-through cache registry, like Artifactory or the open source reference Docker registry. This will allow you to pull images from Docker Hub less frequently, improving your chances of staying under the anonymous usage limit. - Source: dev.to / about 1 year ago

• Concretely, how do you trust the experts? That is, how do you a) identify experts relevant to something and b) determine if they have a consensus (and if so, what it is) on a given topic?

  Like suppose for a second that . . . Idk . . . a product team wants our ci workflows to start using Artifactory. Okay great, I don't know Artifactory integration but I'm going to tell them "Sure, I'll get right on that.". Source: over 1 year ago

• What do I do with large "asset" files?

  If these "assets" have an independent release schedule I would treat them separately (especially if they are externally provided). If they are not built from source then treat them as artefacts, they don't belong in git. You can store the in an artefact repository (like Artifactory of Nexus) or (as u/nekokattt points out) in something like S3. Source: over 1 year ago