Latest Docker plugin update
-
-
I tried the apt clean button. Still looks the same.
Not sure why then. The commit is here - https://github.com/OpenMediaVa…7ae25e6a567186e49f7f315c9 - and the 4.1.0 version in the repo has all commits.
-
For the future of docker, I found this: Cockpit
I've been testing cockpit for months on my omv test VM. It doesn't seem to have any docker features that I can find. It is more for managing one or more machines. Maybe it has more features when running on redhat machines but it is pretty spares on Debian.
-
-
Not sure why then. The commit is here - https://github.com/OpenMediaVa…7ae25e6a567186e49f7f315c9 - and the 4.1.0 version in the repo has all commits.
I checked the dates on the two files involved and they are dated yesterday so I know the 4.1 update took. And a year or so ago I patched those same two files with the same commits. Neither fix worked.
-
I thought the problem was fixed, I did
apt upgrade
and got The property 'apiPort' does not exist in the model 'conf.service.docker'. in the GUI -
@Nefertiti Clear the browser cache
-
@Nefertiti Clear the browser cache
Does not work for me
Code
Alles anzeigenError #0: OMV\AssertException: The property 'apiPort' does not exist in the model 'conf.service.docker'. in /usr/share/php/openmediavault/config/configobject.inc:71 Stack trace: #0 /usr/share/php/openmediavault/config/configobject.inc(186): OMV\Config\ConfigObject->assertExists('apiPort') #1 /usr/share/php/openmediavault/config/configobject.inc(271): OMV\Config\ConfigObject->set('apiPort', '42005', false) #2 /usr/share/php/openmediavault/config/configobject.inc(233): OMV\Config\ConfigObject->setFlatAssoc(Array, false, false) #3 /usr/share/php/openmediavault/config/database.inc(90): OMV\Config\ConfigObject->setAssoc(Array, false) #4 /usr/share/openmediavault/engined/module/docker.inc(31): OMV\Config\Database->get('conf.service.do...') #5 /usr/share/openmediavault/engined/rpc/services.inc(56): OMVModuleDocker->getStatus() #6 [internal function]: OMVRpcServiceServices->getStatus(Array, Array) #7 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array) #8 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('getStatus', Array, Array) #9 /usr/sbin/omv-engined(536): OMV\Rpc\Rpc::call('Services', 'getStatus', Array, Array, 1) #10 {main}
-
Then try the apt clean button in omv-extras. If that doesnt work, you will have to remove the apiPort element from /etc/openmediavault/config.xml. If it is still there, I don’t understand why the code isn’t removing it.
-
Then try the apt clean button in omv-extras. If that doesnt work, you will have to remove the apiPort element from /etc/openmediavault/config.xml. If it is still there, I don’t understand why the code isn’t removing it.
the button did nothing
what part should I remove?
<docker>
<enabled>1</enabled>
<apiPort>42005</apiPort>
<version/>
<versionInfo/>
<sharedfolderref/>
<dockermntent/>
<uuid/>
<orgpath/>
<destpath/>
<cwarn>1</cwarn>
</docker>
</services>
</config> -
I thought the problem was fixed, I did
apt upgrade
and got The property 'apiPort' does not exist in the model 'conf.service.docker'. in the GUII solved it by remove openmediavault-docker-gui, docker-ce in cli, then update sources.list (apt update), install openmediavault-docker-gui 4.1
-
I see there’s a containerd.io update(1.2.0-1), anyone updated and can confirm it’s ok to run?
-
I see there’s a containerd.io update(1.2.0-1), anyone updated and can confirm it’s ok to run?
OK here.
-
OK here.
Thanks gderf. Just ran it and all is good. Figured it'd better to ask first this time. Ha.
-
<apiPort>42005</apiPort>
This line.
-
I see there’s a containerd.io update(1.2.0-1), anyone updated and can confirm it’s ok to run?
It is installed by the docker package as a dependency. So, you don't have any choice.
-
Is the update fixed? Can I update without risk?
-
Is the update fixed? Can I update without risk?
Well I did and never experienced any side effects
-
-
Is the update fixed? Can I update without risk?
If you have a backup, your risk is greatly reduced. That said, most people are able to upgrade without issues. The other users have been able to have their problem solved fairly easily.
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!