I surrender for today. My :ladragonera: #pixelfed instance just works because the docker image is still in memory. My repository is messed up, the customisations are broken and the new docker-compose.yml and .env.docker` are completely failing to load, complaining about empty environment variables that have actual values.
I can't find documentation about how to migrate from v0.11.12 to v0.11.13 when using :docker: #Docker. I am disappointed.
To @dansup and the rest of Pixelfed developers: What you did here is a major change released by just bumping a patch version. That confuse instance maintainers. My instance is unexpectedly screwed up.
They only provide a Dockerfile because it's so convoluted and patched together that it would be impossible to create a decent guide on how to make this stuff work without revealing just how much it's all held together by duct tape. Still, taking a peek at the Dockerfile will clearly reveal the chaos at play.
Everything runs in separate containers, as it should, and they have automatic restarts, as they should. But then they're so tightly bound together with, you guessed it, duct tape, that when one of them fails, the container just restarts automatically, leaving the user wondering why everything failed, with only a cryptic error message.
The main container is controlled by Supervisor - which is necessary because everything crashes very often, but the end user doesn't notice because Supervisor restarts the services. To outsiders, everything works fine (but occasionally throws some errors).
In short, the current trend is to sweep the dirt under the rug. A trendy rug, though!
Sooo....there's a new Mastodon update with security fixes.
As a Linux noob, looking at the update instructions, it doesn't have the usual git checkout commands and things normal updates tell you to do. When I went to update using the exact instructions in the release notes here: https://github.com/mastodon/mastodon/releases/tag/v4.2.6 it didn't update correctly...😬 I hate being such a noob sometimes....
EDIT: I skipped over the commands like a dumbo :facepalm:
Today, in honor of Black History Month, we celebrate the life of Ben Fletcher (April 13, 1890 – 1949), Wobbly and revolutionary. Fletcher joined the Industrial Workers of the World (IWW) in 1912 and became secretary of the IWW District Council in 1913. He also co-founded the interracial Local 8 in 1913. Also in 1913, he led a successful strike of over 10,000 dockers. At that time, roughly one-third of the dockers on the Philadelphia waterfront were black. Another 33% were Irish. And about 33% were Polish and Lithuanian. Prior to the IWW organizing drive, the employers routinely pitted black workers against white, and Polish against Irish. The IWW was one of the only unions of the era that organized workers into the same locals, regardless of race or ethnicity. And its main leader in Philadelphia was an African American, Ben Fletcher.
By 1916, thanks in large part to Fletcher’s organizing skill, all but two of Philadelphia’s docks were controlled by the IWW. And the IWW maintained control of the Philly waterfront for about a decade. After the 1913 strike, Fletcher travelled up and down the east coast organizing dockers. However, he was nearly lynched in Norfolk, Virginia in 1917. At that time, roughly 10% of the IWW’s 1 million members were African American. Most had been rejected from other unions because of their skin color. In 1918, the state arrested him for treason, sentencing him to ten years, for the crime of organizing workers during wartime. He served three years. Fletcher supposedly said to Big Bill Haywood after the trial that the judge had been using “very ungrammatical language. . . His sentences are much too long.”
Are you using #Docker / #containerd / #runc? Congratulations, you won a full container breakout vulnerability via leaked file descriptors that can "lead to full control of the host system".