Zagorath

joined 2 years ago
MODERATOR OF
aom
[–] Zagorath@aussie.zone 1 points 6 hours ago
[–] Zagorath@aussie.zone 19 points 16 hours ago (2 children)

TranscriptionThe "Look What They Need to Mimic a Fraction of Our Power" meme, showing two frames of Omni-Man from Invincible. Omni-Man has an image of Tux, the Linux penguin, superimposed over him in both.

In the first frame, he look out at a screenshot of a YouTube thumbnail, which reads "UPDATE ALL SOFTWARE AT ONCE! ONE CLICK! FAST & EASY! 100% FREE!", and a title which reads "Update All Software on Windows PC at Once | One-Click Method (Fast & Free)."

In the second frame, he says "Look what they need to mimic a fraction of our power".

[–] Zagorath@aussie.zone 55 points 16 hours ago (1 children)

Tux's right eye being occluded by the guy's black hair, and his left eye being partly shaded into a more angular shape makes it look like he's giving an evil smirk.

[–] Zagorath@aussie.zone 7 points 18 hours ago (1 children)

Ce n'est pas seulement dans la culture anglophone. Selon Explain XKCD, il à commencé en français.

[–] Zagorath@aussie.zone 21 points 18 hours ago (1 children)
[–] Zagorath@aussie.zone 10 points 1 day ago (1 children)

!vampires@lemmy.zip

!bun_alert_system@lemmy.sdf.org

!ankmemes@sh.itjust.works

!nominativedeterminism@feddit.uk

!rpgmemes@ttrpg.network

!pathfinder@ttrpg.network

And I'll also second @squirrel@piefed.kobel.fyi's recommendation of !dailygames@lemmy.zip. I finally got the bot I run for that community up and running on a computer that isn't my desktop, so make sure you haven't disabled bot accounts!

[–] Zagorath@aussie.zone 1 points 1 day ago

Edit: Who the hell is taking this seriously enough to downvote?

amarynthia@sh.itjust.works and Passerby6497@lemmy.world

[–] Zagorath@aussie.zone 1 points 1 day ago (1 children)

Thanks! I genuinely wasn't sure how much RAM would be necessary, and would have probably seriously considered 8 GB enough if I hadn't gotten the feedback.

[–] Zagorath@aussie.zone 2 points 1 day ago (1 children)

I've no comments on RISC-V, but I agree that a move towards ARM in the Windows & Linux worlds would seem sensible. I would guess it hasn't happened for the same reason IPv6 hasn't taken over. Too much momentum. Too many developers still working in an x86 world, too many legacy apps that won't easily run on ARM, too many hardware manufacturers each making the individual choice to keep making the current-popular option. Apple could transition because they're the single gatekeeper. They make the decision, and everybody else who wants to use a Mac has to follow along. I'm going to guess that the control they have over the hardware and the software also means Rosetta 2 works a hell of a lot better than Microsoft's Prism. (I can't say for sure, having never used an ARM-based Windows machine or an ARM-based Mac.)

In terms of heat, what kind of room do you have it in? Somewhere with good natural airflow, or away in a closet somewhere?

[–] Zagorath@aussie.zone 1 points 1 day ago (1 children)

I guess I have the same question for you as I did for curbstickle. What's the advantage of doing things that way with VMs, vs running Docker containers? How does it end up working?

[–] Zagorath@aussie.zone 2 points 1 day ago (1 children)

Interesting. I've never really played around with that style of VM-based server architecture before. I've always either used Docker (& Kubernetes) or ran things on bare metal.

If you're willing to talk a bit more about how it works, advantages of it, etc., I'd love to hear. But I sincerely don't want to put any pressure and won't be at all offended if you don't have the time or effort.

[–] Zagorath@aussie.zone 1 points 1 day ago

I'm not sure I agree with your definition of walled garden. I'd say it's a place that's designed to be nice and easy to use within the bounds designed for you (the garden), but which protects the user from doing something that might harm them, even if that "protection" comes at the cost of being able to do other things they want to do, in a kind of paternalistic way (the wall). The classic example would be iOS, where the only apps you can install are the ones Apple has approved for you. Getting apps from the open web the way you would on Windows, macOS, or Linux could be dangerous!

Your description of:

you may run into roadblocks doing things that way, yes. You are pretty much limited to what’s on their (vast) catalog

Makes it sound very much a walled garden to me. Not as high-walled as iOS of course, but it's a spectrum.

But anyway, it's basically semantics. Not that important what you call it.

 

So after months of dealing with problems trying to get the stuff I want to host working on my Raspberry Pi and Synology, I've given up and decided I need a real server with an x86_64 processor and a standard Linux distro. So I don't continue to run into problems after spending a bunch more, I want to seriously consider what I need hardware-wise. What considerations do I need to think about in this?

Initially, the main things I want to host are Nextcloud, Immich (or similar), and my own Node bot @DailyGameBot@lemmy.zip (which uses Puppeteer to take screenshots—the big issue that prevents it from running on a Pi or Synology). I'll definitely want to expand to more things eventually, though I don't know what. Probably all/most in Docker.

For now I'm likely to keep using Synology's reverse proxy and built-in Let's Encrypt certificate support, unless there are good reasons to avoid that. And as much as it's possible, I'll want the actual files (used by Nextcloud, Immich, etc.) to be stored on the Synology to take advantage of its large capacity and RAID 5 redundancy.

Is a second-hand Intel-based mini PC likely suitable? I read one thing saying that they can have serious thermal throttling issues because they don't have great airflow. Is that a problem that matters for a home server, or is it more of an issue with desktops where people try to run games? Is there a particular reason to look at Intel vs AMD? Any particular things I should consider when looking at RAM, CPU power, or internal storage, etc. which might not be immediately obvious?

Bonus question: what's a good distro to use? My experience so far has mostly been with desktop distros, primarily Kubuntu/Ubuntu, or with niche distros like Raspbian. But all Debian-based. Any reason to consider something else?

 

cross-posted from: https://aussie.zone/post/28062823

I'm trying to set up Nextcloud using the AIO Docker install onto my Synology.

I got through the first stage of setup, and navigated to the /containers page. It shows all containers as "Starting", with a yellow dot. Except for the Fulltextsearch, which is Stopped red (due to me stopping it, after I realised I had installed it despite my platform not supporting Seccomp, but the "Optional containers" checkbox being greyed out even when it’s stopped).

Many of these containers show as green/healthy in the DSM Container Manager even though the /containers page doesn't show them as such.

Logs for the different containers:

Mastercontainer logs:

Trying to fix docker.sock permissions internally...
Adding internal www-data to group root
DOCKER_API_VERSION was found to be set to '1.43'.
Please note that only v1.44 is officially supported and tested by the maintainers of Nextcloud AIO.
So you run on your own risk and things might break without warning.
WARNING: No kernel memory TCP limit support
WARNING: No cpu cfs quota support
WARNING: No cpu cfs period support
WARNING: No blkio throttle.read_bps_device support
WARNING: No blkio throttle.write_bps_device support
WARNING: No blkio throttle.read_iops_device support
WARNING: No blkio throttle.write_iops_device support
WARNING: No kernel memory TCP limit support
WARNING: No cpu cfs quota support
WARNING: No cpu cfs period support
WARNING: No blkio throttle.read_bps_device support
WARNING: No blkio throttle.write_bps_device support
WARNING: No blkio throttle.read_iops_device support
WARNING: No blkio throttle.write_iops_device support
Initial startup of Nextcloud All-in-One complete!
You should be able to open the Nextcloud AIO Interface now on port 8080 of this server!
E.g. https://internal.ip.of.this.server:8080/
⚠️ Important: do always use an ip-address if you access this port and not a domain as HSTS might block access to it later!

If your server has port 80 and 8443 open and you point a domain to your server, you can get a valid certificate automatically by opening the Nextcloud AIO Interface via:
https://your-domain-that-points-to-this-server.tld:8443/
/usr/lib/python3.12/site-packages/supervisor/options.py:13: UserWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html. The pkg_resources package is slated for removal as early as 2025-11-30. Refrain from using this package or pin to Setuptools<81.
  import pkg_resources
{"level":"warn","ts":1766322552.6626272,"msg":"failed to set GOMAXPROCS","error":"open /sys/fs/cgroup/cpu/cpu.cfs_quota_us: no such file or directory"}
{"level":"info","ts":1766322552.6628811,"msg":"GOMEMLIMIT is updated","package":"github.com/KimMachineGun/automemlimit/memlimit","GOMEMLIMIT":3671407411,"previous":9223372036854775807}
{"level":"info","ts":1766322552.6629462,"msg":"using config from file","file":"/Caddyfile"}
{"level":"info","ts":1766322552.6645825,"msg":"adapted config to JSON","adapter":"caddyfile"}
{"level":"info","ts":1766322552.6664238,"msg":"serving initial configuration"}
[mpm_event:notice] [pid 152:tid 152] AH00489: Apache/2.4.66 (Unix) OpenSSL/3.5.4 configured -- resuming normal operations
[core:notice] [pid 152:tid 152] AH00094: Command line: 'httpd -D FOREGROUND'
NOTICE: fpm is running, pid 157
NOTICE: ready to handle connections
NOTICE: PHP message: 404 Not Found
Type: Slim\Exception\HttpNotFoundException
Code: 404
Message: Not found.
File: /var/www/docker-aio/php/vendor/slim/slim/Slim/Middleware/RoutingMiddleware.php
Line: 76
Trace: #0 /var/www/docker-aio/php/vendor/slim/slim/Slim/Routing/RouteRunner.php(62): Slim\Middleware\RoutingMiddleware->performRouting(Object(GuzzleHttp\Psr7\ServerRequest))
#1 /var/www/docker-aio/php/vendor/slim/csrf/src/Guard.php(482): Slim\Routing\RouteRunner->handle(Object(GuzzleHttp\Psr7\ServerRequest))
#2 /var/www/docker-aio/php/vendor/slim/slim/Slim/MiddlewareDispatcher.php(178): Slim\Csrf\Guard->process(Object(GuzzleHttp\Psr7\ServerRequest), Object(Slim\Routing\RouteRunner))
#3 /var/www/docker-aio/php/vendor/slim/twig-view/src/TwigMiddleware.php(117): Psr\Http\Server\RequestHandlerInterface@anonymous->handle(Object(GuzzleHttp\Psr7\ServerRequest))
#4 /var/www/docker-aio/php/vendor/slim/slim/Slim/MiddlewareDispatcher.php(129): Slim\Views\TwigMiddleware->process(Object(GuzzleHttp\Psr7\ServerRequest), Object(Psr\Http\Server\RequestHandlerInterface@anonymous))
#5 /var/www/docker-aio/php/src/Middleware/AuthMiddleware.php(53): Psr\Http\Server\RequestHandlerInterface@anonymous->handle(Object(GuzzleHttp\Psr7\ServerRequest))
#6 /var/www/docker-aio/php/vendor/slim/slim/Slim/MiddlewareDispatcher.php(283): AIO\Middleware\AuthMiddleware->__invoke(Object(GuzzleHttp\Psr7\ServerRequest), Object(Psr\Http\Server\RequestHandlerInterface@anonymous))
#7 /var/www/docker-aio/php/vendor/slim/slim/Slim/Middleware/ErrorMiddleware.php(77): Psr\Http\Server\RequestHandlerInterface@anonymous->handle(Object(GuzzleHttp\Psr7\ServerRequest))
#8 /var/www/docker-aio/php/vendor/slim/slim/Slim/MiddlewareDispatcher.php(129): Slim\Middleware\ErrorMiddleware->process(Object(GuzzleHttp\Psr7\ServerRequest), Object(Psr\Http\Server\RequestHandlerInterface@anonymous))
#9 /var/www/docker-aio/php/vendor/slim/slim/Slim/MiddlewareDispatcher.php(73): Psr\Http\Server\RequestHandlerInterface@anonymous->handle(Object(GuzzleHttp\Psr7\ServerRequest))
#10 /var/www/docker-aio/php/vendor/slim/slim/Slim/App.php(209): Slim\MiddlewareDispatcher->handle(Object(GuzzleHttp\Psr7\ServerRequest))
#11 /var/www/docker-aio/php/vendor/slim/slim/Slim/App.php(193): Slim\App->handle(Object(GuzzleHttp\Psr7\ServerRequest))
#12 /var/www/docker-aio/php/public/index.php(200): Slim\App->run()
#13 {main}
Tips: To display error details in HTTP response set "displayErrorDetails" to true in the ErrorHandler constructor.
NOTICE: Terminating ...
NOTICE: exiting, bye-bye!
[mpm_event:notice] [pid 152:tid 152] AH00491: caught SIGTERM, shutting down

Database logs:

+ rm -rf '/var/lib/postgresql/data/*'
+ touch /mnt/data/initial-cleanup-done
+ set +ex
chmod: /var/run/postgresql: Operation not permitted
The files belonging to this database system will be owned by user "postgres".
This user must also own the server process.

The database cluster will be initialized with locale "en_US.utf8".
The default database encoding has accordingly been set to "UTF8".
The default text search configuration will be set to "english".

Data page checksums are disabled.

fixing permissions on existing directory /var/lib/postgresql/data ... ok
creating subdirectories ... ok
selecting dynamic shared memory implementation ... posix
selecting default "max_connections" ... 100
selecting default "shared_buffers" ... 128MB
selecting default time zone ... Australia/Brisbane
creating configuration files ... ok
running bootstrap script ... ok
sh: locale: not found
[30] WARNING:  no usable system locales were found
performing post-bootstrap initialization ... ok
initdb: warning: enabling "trust" authentication for local connections
initdb: hint: You can change this by editing pg_hba.conf or using the option -A, or --auth-local and --auth-host, the next time you run initdb.
syncing data to disk ... ok


Success. You can now start the database server using:

    pg_ctl -D /var/lib/postgresql/data -l logfile start

waiting for server to start....
[36] LOG:  starting PostgreSQL 17.7 on x86_64-pc-linux-musl, compiled by gcc (Alpine 15.2.0) 15.2.0, 64-bit
[36] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
[39] LOG:  database system was shut down at 2025-12-21 23:21:07 AEST
[36] LOG:  database system is ready to accept connections
 done
server started
CREATE DATABASE


/usr/local/bin/docker-entrypoint.sh: running /docker-entrypoint-initdb.d/init-user-db.sh
CREATE ROLE
ALTER DATABASE
+ touch /mnt/data/initialization.failed
+ psql -v ON_ERROR_STOP=1 --username nextcloud --dbname nextcloud_database
GRANT
GRANT
+ rm /mnt/data/initialization.failed

waiting for server to shut down....2025-12-21 23:21:12.597 AEST [36] LOG:  received fast shutdown request
+ set +ex
[36] LOG:  aborting any active transactions
[36] LOG:  background worker "logical replication launcher" (PID 42) exited with exit code 1
[37] LOG:  shutting down
[37] LOG:  checkpoint starting: shutdown immediate
[37] LOG:  checkpoint complete: wrote 934 buffers (5.7%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.805 s, sync=0.674 s, total=2.456 s; sync files=308, longest=0.322 s, average=0.003 s; distance=4260 kB, estimate=4260 kB; lsn=0/19163B0, redo lsn=0/19163B0
[36] LOG:  database system is shut down
 done
server stopped

PostgreSQL init process complete; ready for start up.

[14] LOG:  starting PostgreSQL 17.7 on x86_64-pc-linux-musl, compiled by gcc (Alpine 15.2.0) 15.2.0, 64-bit
[14] LOG:  listening on IPv4 address "0.0.0.0", port 5432
[14] LOG:  listening on IPv6 address "::", port 5432
[14] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
[57] LOG:  database system was shut down at 2025-12-21 23:21:15 AEST
[14] LOG:  database system is ready to accept connections
[55] LOG:  checkpoint starting: time
[55] LOG:  checkpoint complete: wrote 48 buffers (0.3%); 0 WAL file(s) added, 0 removed, 0 recycled; write=4.592 s, sync=0.911 s, total=6.666 s; sync files=13, longest=0.172 s, average=0.071 s; distance=270 kB, estimate=270 kB; lsn=0/1959CE8, redo lsn=0/1959C58
++ rm -f /mnt/data/database-dump.sql.temp
++ touch /mnt/data/export.failed
++ pg_dump --username nextcloud nextcloud_database
++ rm -f /mnt/data/database-dump.sql
++ mv /mnt/data/database-dump.sql.temp /mnt/data/database-dump.sql
++ pg_ctl stop -m fast
[14] LOG:  received fast shutdown request
[14] LOG:  aborting any active transactions
[14] LOG:  background worker "logical replication launcher" (PID 60) exited with exit code 1
[55] LOG:  shutting down
[55] LOG:  checkpoint starting: shutdown immediate
[55] LOG:  checkpoint complete: wrote 0 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.001 s, sync=0.001 s, total=0.502 s; sync files=0, longest=0.000 s, average=0.000 s; distance=0 kB, estimate=243 kB; lsn=0/1959D98, redo lsn=0/1959D98
[14] LOG:  database system is shut down
waiting for server to shut down.... done
server stopped
++ rm /mnt/data/export.failed
++ echo 'Database dump successful!'
++ set +x
Database dump successful!
Setting postgres values...
chmod: /var/run/postgresql: Operation not permitted

PostgreSQL Database directory appears to contain a database; Skipping initialization

[14] LOG:  starting PostgreSQL 17.7 on x86_64-pc-linux-musl, compiled by gcc (Alpine 15.2.0) 15.2.0, 64-bit
[14] LOG:  listening on IPv4 address "0.0.0.0", port 5432
[14] LOG:  listening on IPv6 address "::", port 5432
[14] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
[24] LOG:  database system was shut down at 2025-12-21 23:49:29 AEST
[14] LOG:  database system is ready to accept connections

Nextcloud logs:

Waiting for database to start...
Waiting for database to start...
Waiting for database to start...

Redis logs:

Memory overcommit is disabled but necessary for safe operation
See https://github.com/nextcloud/all-in-one/discussions/1731 how to enable overcommit
Redis has started
# WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
# WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.

I don’t think Redis is related to my current problem, but I suspect they may be an issue later...

Configuration

AIO compass.yaml file:

name: nextcloud-aio
services:
  nextcloud-aio-mastercontainer:
    image: ghcr.io/nextcloud-releases/all-in-one:latest
    init: true
    restart: always
    container_name: nextcloud-aio-mastercontainer
    volumes:
      - nextcloud_aio_mastercontainer:/mnt/docker-aio-config
      - /run/docker.sock:/var/run/docker.sock:ro
    network_mode: bridge
    ports:
      - 8080:8080
    environment:
      APACHE_PORT: 11000
      APACHE_IP_BINDING: 127.0.0.1
      DOCKER_API_VERSION: 1.43 # As far as I can tell, this is the version supported on Synology when running "docker version | grep API"
      NEXTCLOUD_DATADIR: /volume1/nextcloud
      WATCHTOWER_DOCKER_SOCKET_PATH: /run/docker.sock
      COLLABORA_SECCOMP_DISABLED: true

volumes:
  nextcloud_aio_mastercontainer:
    name: nextcloud_aio_mastercontainer

Does anyone have any idea of how to get this working? Or of good troubleshooting steps to try?

 

Most of the threads I've found on other sites (both Reddit and the Synology forums) have basically said "go with Docker". But what do you actually gain from this?

People suggest it's more up-to-date, and maybe for some packages that's true? But for Nextcloud specifically it looks pretty good. 32.0.3 came out 1 day ago and isn't yet supported, but the version immediately preceding that, from 3 weeks ago, is.

I've never done Nextcloud before, but I would assume installing it via the Package Center would be way easier to install and to keep up-to-date than Docker. So what's the reason everyone recommends Docker? Is it easier to extend?

 

Text TranscriptionA series of Tweets, each a reply to the previous.

  1. ABC News @ABC: Scientists have discovered a giant new species of stick insect in Australia, which is over 15 inches long and researchers say may be the heaviest insect in the country. [With a picture of a brown stick insect among some green leaves.]
  2. mary @theoceanblooms: can I ask a question: how does something like this go undiscovered until now
  3. soul nate @MNateShyamalan: Entomologist here 🙋‍♂️🤓🐜 Great question! It may seem surprising that the scientific community could miss an entire bug species after all this time, especially when it's THIS big. The answer might surprise you more 👀 Let's dive in 👇🧵 (1/?)
  4. soul nate @MNateShyamalan: he look like stick (2/2)
view more: next ›