Thanks Todd. I have tried that before but it didnt seem to work for me.
I did an export IMGADM_INSECURE=1
Then typed env and verified it was set. Then ran imgadm but i still got the
error. Granted I am using the skylime version of smartos which has the fix to
allow imgadm to work with docker reg
On 18 Apr 2018, at 17:32, Rob Seastrom wrote:
On Apr 18, 2018, at 9:23 AM, Jussi Sallinen wrote:
The actual email data resides in a delegated dataset mounted on
/data.
Delegated or loopback-mounted? I loopback-mount my (persistent) email
stuff on /home.
I loopback-mount my data files an
Thanks Jussi
I'll give it a go your way.
Kevin Ratcliffe
Sent from ProtonMail
‐‐‐ Original Message ‐‐‐
On 18 April 2018 2:23 PM, Jussi Sallinen wrote:
>
>
> On 17/04/2018 23.52, k...@protonmail.com wrote:
>
> > Thanks for the input Jussi.
> >
> > The reprovision just hung ar
On 18 Apr 2018, at 18.32, Rob Seastrom wrote:
>
> Delegated or loopback-mounted? I loopback-mount my (persistent) email stuff
> on /home.
Delegated in this case.
Loooback-mount for instances which need to share data, ie. WWW-backend and
separate customer instance for uploading files through S
Hi Eugene,
I myself don't know of a way to update the root CA, I think node
programs (which is what imgadm uses) include the certs in the binary
itself (using static linking).
If you are using imgadm you can set the IMGADM_INSECURE environment
variable as a workaround:
IMGADM_INSECURE=
> On 18 Apr 2018, at 12:44, Rob Seastrom wrote:
>
>
> +1. I’ve tripped over this as well (not with docker but my letsencrypt certs
> appear invalid from the global zone.
I think this is https://github.com/joyent/smartos-live/issues/450
Chris
---
smar
> On Apr 18, 2018, at 9:23 AM, Jussi Sallinen wrote:
>
> The actual email data resides in a delegated dataset mounted on /data.
Delegated or loopback-mounted? I loopback-mount my (persistent) email stuff on
/home.
-r
---
smartos-discuss
Archives: h
On 17/04/2018 23.52, k...@protonmail.com wrote:
Thanks for the input Jussi.
The reprovision just hung around for five minutes then failed. Looking at the
log sent me cross-eyed on this notebook.
The longer term plan was to document a process for the reprovision for future
automation with Ans
+1. I’ve tripped over this as well (not with docker but my letsencrypt certs
appear invalid from the global zone.
-r
> On Apr 18, 2018, at 07:01, Eugene Lee wrote:
>
> Hi,
>
> Is it possible to update the root CA certificate files installed in SmartOS?
> I am trying to download an image
Hi,
Is it possible to update the root CA certificate files installed in SmartOS? I
am trying to download an image from a private docker registry but the SSL
certificate I have installed on the private docker registry is not recognised.
It is not a Self Signed certificate, but it is issued by
10 matches
Mail list logo
