Hi all,
it seems that the Local Volumes add-on is not compatible with the 2.3.2 FlyWheel release, and the new 1.3.0 custom environment. See my issue on GH:
Now, because I really need this functionality, I’d like to go and fix myself, but without some documentation on the APIs exposed by Local, that’s pretty impossible.
If someone from the core team is reading, please give me at least some directions on which APIs are changed in a breaking way, and if possible provide the new syntax.
The culprit of the Volumes add-on is the following snippet of code:
docker().createContainer({
'Image': image.Id,
'Cmd': _this5.state.path,
'Tty': true,
'ExposedPorts': exposedPorts,
'HostConfig': {
'Binds': _this5.state.volumes.map(function (volume) {
var source = _this5.formatDockerPath(volume.source);
return formatHomePath(source) + ':' + volume.dest;
}),
'PortBindings': portBindings
}
}).then(function (container) {
site.container = container.id;
if ('clonedImage' in site) {
if (typeof site.clonedImage != 'string') {
site.clonedImage.push(image.Id);
} else {
site.clonedImage = [site.clonedImage, image.Id];
}
} else {
site.clonedImage = image.Id;
}
siteData.updateSite(siteID, site);
startSite(site).then(function () {
sendEvent('updateSiteStatus', siteID, 'running');
_this5.setState({
provisioning: false
});
context.notifier.notify({
title: 'Volumes Remapped',
message: 'Volumes for ' + site.name + ' have been remapped.'
});
});
docker().getContainer(oldSiteContainer).remove();
});
It’s pretty straightforward, and I simply need to know what’s not compatible anymore in 2.3.2 / custom 1.3.0
Thanks for your support,
Paolo