container-image-stream ignored
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Low
|
Joseph Phillips |
Bug Description
juju 2.4.3
Deployed containers do not appear to honour "container-
Before (when set to released), from container A:
~$ juju model-config container-
released
~$ cat /etc/cloud/
build_name: server
serial: 20180823
~$ sudo lxc image list ubuntu-
+------
| ALIAS | FINGERPRINT | PUBLIC | DESCRIPTION | ARCH | SIZE | UPLOAD DATE |
+------
| b (9 more) | f613aca927fc | yes | ubuntu 18.04 LTS s390x (daily) (20180830) | s390x | 165.83MB | Aug 30, 2018 at 12:00am (UTC) |
+------
After, from container B:
~$ juju model-config container-
daily
... juju add-unit ...
~$ cat /etc/cloud/
build_name: server
serial: 20180823
Changed in juju: | |
status: | New → Incomplete |
assignee: | nobody → Joseph Phillips (manadart) |
Changed in juju: | |
importance: | Undecided → Medium |
status: | New → Triaged |
There are a few things that might be at play here.
First, can you verify that there is no value set for "container- image-metadata- url"?
I had a quick scan of the streams on cloud-images. ubuntu. com and there does seem to be both released and daily builds for that architecture. The default is to fall back from released to daily if not found.
Second, note that if Juju has deployed a container, the image will be saved on the machine with a juju-specific alias. This alias does not factor the stream, so if you have an image, change the stream, and deploy a container on the same host, then the alias hit will give the same image as before.
Can you verify whether this is the case?