Juju client on centos with NFS homes

1

Looking for advice on how to install the juju client on centos7 where users has home directories on NFS.

The NFS situation (which is common) causes issues with snap versions, but perhaps that has changed over time since we last tried this a few years ago?

Otherwise, is there a recommended way to distribute the Juju client in a shared environment? Are there RPM:s? Are there Appimages?

2

That was one of the reasons we moved away from snaps in our charms. There are many compatibility problems in there.

I’d love to see Juju and charmcraft packaged as deb/rpms. That would make Juju available for non-Ubuntu OSes :slight_smile: This is one of the reasons Juju is not used in the wild: it requires people to use Ubuntu, and many people use other linux distributions.

2 Likes
3

If you haven’t tried the snapped juju on CentOS lately, you may wish to try again.

You may find you need to use the environment variable JUJU_DATA as such:

sudo snap install --classic juju
export JUJU_DATA=$HOME/.local/share/juju
juju bootstrap ....

There are binaries built and distributed on the github project here, but they are not packaged as RPM/DEB.

4

Its a pain and awkward situation having to go through snap to get to juju on distros heavily tailored to rpm.

It requires also to get snapd running, which is yet another obstacle on centos/rhel.

I guess it’s a dead end unless someone would take on the task of trying to get a juju client into a rpmbuild.

1 Like
5

Not only to distros tailored to RPM, but any distro other than Ubuntu.

For the case you mentioned on the first post here, snapd will not work reliably if the /home/user is in a NFS share. So, Snaps don’t work… maybe we need a Launchpad ticket to request an RPM and DEB for Juju and its components.

1 Like
6

All binaries for juju can be found on the Juju download page. These have been signed and verified (see signatures).

One might do the following:

$ curl -fL https://launchpad.net/juju/2.9/2.9.21/+download/juju-2.9.21-linux-amd64.tar.xz --output juju-2.9.21-linux-amd64.tar.xz
$ md5sum juju-2.9.21-linux-amd64.tar.xz
b08e2151dd8ba9f7ae39ee2e27c5a360  juju-2.9.21-linux-amd64.tar.xz

That should match the md5 from the server.

See the Verifying a download documentation on launchpad.

2 Likes