You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
the AMI images have unattended upgrades set it seems - which can lead to an error like:
E: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 4587 (unattended-upgr)E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
in this particular case there is no need to install anything anyway - but i would guess that this is slowing things down, soaking net io and generally being undesirable - and we should be able to install without it failing
The text was updated successfully, but these errors were encountered:
this makes me wonder what else is running on these AMIs and whether there is a more lightweight base image we could use that doesnt do this kind of thing - if its a "server" install its probably set up to serve php or similar
the AMI images have unattended upgrades set it seems - which can lead to an error like:
in this particular case there is no need to install anything anyway - but i would guess that this is slowing things down, soaking net io and generally being undesirable - and we should be able to install without it failing
The text was updated successfully, but these errors were encountered: