upgrade os at docker
after las update gitlab ce (now i have version 13.9.1), it wrote me, that ubuntu 16.04 will be depredicate.

if i dont find a way how to upgrade os at docker, what to do?

how to update os at docker? if it is not possible, how update docker image without data lost?

i have docker image at windows 10…
what to do::

docker exec -it gitlab /bin/bash

then

apt install update-manager-core

then

do-release-upgrade
hi mike, thanks for bringing this to our attention, i can confirm that i’m aware of this issue and a fix is in progress. i expect the latest version to be available the debian/rpm repositories in the coming days.

one short term work around would be to download the .deb or .rpm file directly from th… hello and welcome [@jhmauritz](/u/jhmauritz).

yes, changing the variables should be enough to connect to the server, and using docker-compose is absolutely a viable option.

if the server is publicly available you should configure ssl as well, otherwise your connections to it won’t be secure.

mind that although y… for anyone stumbling upon this thread, check out how to use inherit += "rpi-update-firmware" to enable boot partition updates. official tutorial is available here: [updating raspberry pi boot firmware files using yocto project and mender](https://hub.mender.io/t/updating-raspberry-pi-boot-firmware-files-using-yocto-project-and-mender/1719)

this was merged in master a few day ago ([pr#953](https://github.com/mendersoftware/meta-mender/pull/953)), and should b… hi obin, there is no option to upgrade the vcenter from prism. you will have to use the vmware procedure to upgrade the vcenter. so, you do not need to take any action in prism for the vcenter upgrade and there will be no impact on the nutanix cluster. you can upgrade the esxi hosts from the prism later. my legendary persistence has paid off!

from looking at other dockerfiles in the repo, i discovered that the js files needed were not being copied to the image in the original dockerfile i used to base this on. no wonder it was looking everywhere and not finding anything!

:point\_right: copy ./build… sometimes one or both of these patches help, especially if the system is showing high ram and/or cpu usage when checking updates:
https://support.microsoft.com/en-us/kb/3050265




https://support.microsoft.com/en-us/kb/3102810﻿﻿
﻿ [image] soydepr:

certbot: error: unrecognized arguments: renewal

you should still be able to renew. the command is:

certbot-auto renew We identified a scenario where locking could occur, and released a fix in version 13.0.1. If anyone is experiencing this issue, please upgrade to 13.0.1. that is where i'd start as well. osi...
so:
1. physical link (maybe check the patch panel and the cabling that's involved in connecting to the computer, maybe swap cables and try a usb to ethernet adapter to rules the nic out.
2. data link - check the switches and switchports on the way. maybe try to use different portts
3. network - most likely not an issue if all the other computers are working fine...
etc.
but this is pretty much it: you need to change the boot order so it checks the HDD before the floppy, cdrom etc...



btw a new pc means you will have to reinstall windows