| 2019-03-20 17:44:46 |
John A Meinel |
description |
With the new feature to install MongoDB from a snap, it became much more relevant to have a snap store proxy setup for the LXD provider. Otherwise it downloads all of core core 18 and juju-db on every bootstrap.
However, *during* the bootstrap process, the snap settings are not set yet:
2019-03-20 17:08:11 INFO juju.mongo mongo.go:511 Ensuring mongo server is running; data directory /var/snap/juju-db/common; port 37017 2019-03-20 17:08:11 INFO juju.service.snap snap.go:382 preparing command: snap install --stable --jailmode core 2019-03-20 17:08:11 INFO juju.service.snap snap.go:392 preparing command: snap install --edge --jailmode juju-db 2019-03-20 17:08:11 INFO juju.service.snap snap.go:342 command: snap install --stable --jailmode core s^C
root@juju-52a250-0:~# sudo snap status
error: unknown command "status", see 'snap help'
root@juju-52a250-0:~# sudo snap get core
Key Value
cloud {...}
refresh {...}
seed {...}
root@juju-52a250-0:~# sudo snap get core -d
{
"cloud": {
"name": "unknown"
},
"refresh": {
"hold": "2019-03-20T19:06:41.995742809Z"
},
"seed": {
"loaded": true
}
}
We *definitely* need to check for them before we run 'snap install' of *anything*.
While for local development this is a 'nice to have'. If we get to production, they won't have outbound access *at all* without the proxy being set.
These are the settings "snap-store-id", and "snap-store-assertions" than need to get properly handled early. |
With the new feature to install MongoDB from a snap, it became much more relevant to have a snap store proxy setup for the LXD provider. Otherwise it downloads all of core core 18 and juju-db on every bootstrap.
However, *during* the bootstrap process, the snap settings are not set yet:
2019-03-20 17:08:11 INFO juju.mongo mongo.go:511 Ensuring mongo server is running; data directory /var/snap/juju-db/common; port 37017 2019-03-20 17:08:11 INFO juju.service.snap snap.go:382 preparing command: snap install --stable --jailmode core 2019-03-20 17:08:11 INFO juju.service.snap snap.go:392 preparing command: snap install --edge --jailmode juju-db 2019-03-20 17:08:11 INFO juju.service.snap snap.go:342 command: snap install --stable --jailmode core s^C
root@juju-52a250-0:~# sudo snap status
error: unknown command "status", see 'snap help'
root@juju-52a250-0:~# sudo snap get core
Key Value
cloud {...}
refresh {...}
seed {...}
root@juju-52a250-0:~# sudo snap get core -d
{
"cloud": {
"name": "unknown"
},
"refresh": {
"hold": "2019-03-20T19:06:41.995742809Z"
},
"seed": {
"loaded": true
}
}
We *definitely* need to check for them before we run 'snap install' of *anything*.
While for local development this is a 'nice to have'. If we get to production, they won't have outbound access *at all* without the proxy being set.
These are the settings "snap-store-proxy", and "snap-store-assertions" than need to get properly handled early.
(in the first test, I accidentally used 'snap-store-id' which is the ProxyConfig value, not 'snap-store-proxy' which is the environs/config value. However, I fixed that, and bootstrapped a second time, and saw the same behavior. We are running 'snap install' before we have configured snap-store-proxy.) |
|
