this post was submitted on 05 Sep 2023
6 points (100.0% liked)

Ubuntu Server

11 readers
1 users here now

Like the name suggests, this community is based on the Linux operating system (unofficial) Ubuntu Server. We share ideas and resources, provide support and maybe have a little fun along the way. Please post/send suggestions for new topics to the mods. Have a great day!

Ubuntu Server Edition FAQ page

Its ease of use, ability to customise and capacity to run on a wide range of hardware makes Ubuntu the most popular server choice of the cloud age. This FAQs page provides answers to technical questions.

Ubuntu Server Guide

The Ubuntu Server Guide is available on the official Ubuntu Page. For convenience we have put a shortcut on here. Please check it if you need help with initial setup.

Awesome Selfhosted Projects

The Awesome Selfhosted Project is a community sourced github-page which contains tons of useful information and ideas for projects for Linux Servers (and therefore Ubuntu as well).

Rules

  1. No Advertising (open source is allowed)
  2. No spamming
  3. No misdirected links
  4. No NSFW
  5. Don't be a jerk
  6. Thorough descriptions

If you have any additions to this sidebar, please feel free to message us or make a post about it. :)

founded 1 year ago
MODERATORS
[email protected]
6
Newest docker update wrecked my sytem for an hour (discuss.tchncs.de)
submitted 1 year ago by [email protected] to c/[email protected]
2 comments fedilink hide all child comments
 

Hi folks!

System

I‘m running ubuntu 22.04.2 on an old terra miniserver g2 with a xeon 4 core without mt, 16 gb ram and a redneck engineered usb-stick/ssd/hdd config which was supposed to be temporary. I have a 3-2-1 Backup solution though.

What happened

Today I opened my grafana panel and found it not working. Portainer told me that my influxdb container is down. So I ssh‘d in and the system told me it needed a restart. So I ran an update (including docker) and restarted. Nothing worked. Turns out, my dns (pihole) was offline. I found that docker was down completely. Grep syslog told me that docker couldn’t start since the docker config was defective.

An old mistake coming to haunt me

Turns out I had made a „weird“ docker config, using the /erc/docker/daemon.json. Instead of { „asset“:“value“, „asset“:“value“} I had done {„asset“:“value“}{„asset“:“value“}.

This led to the error but didn’t bother me for over a year and worked well. Something in this new update must have enforced the syntax or soenthing.

TL;DR

I made a janky docker daemon.json conf and got fucked by the update today. If your docker stops working, check the logs/daemon.json

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 3 points 1 year ago (1 children)

Thanks for sharing!

[–] [email protected] 1 points 1 year ago

You’re very welcome! Thanks for the support!