Skip Navigation

Posts
15
Comments
181
Joined
2 yr. ago

  • 100% this. And Lenovos and HPs designed for the business market generally are a pleasure to work on (in the hardware sense) if you need, with good manuals and secondhand spare parts.

  • I run nearly all my Docker workloads with their data just in the home directory of the VM (or LXC actually since that's how I roll) I'm running them in, but a few have data on my separate NAS via and NFS share - so through a switch etc with no problems - just slowish.

  • Great. There's two volumes there - firefly_iii_upload & firefly_iii_db.

    You'll definitely want to docker compose down first (to ensure the database is not being updated), then:

     
        
    docker run --rm \
      -v firefly_iii_db:/from \
      -v $(pwd):/to \
      alpine sh -c "cd /from && tar cf /to/firefly_iii_db.tar ."
    
    
      

    and

     
        
    docker run --rm \
      -v firefly_iii_upload:/from \
      -v $(pwd):/to \
      alpine sh -c "cd /from && tar cf /to/firefly_iii_upload.tar ."
    
    
      

    Then copy those two .tar files to the new VM. Then create the new empty volumes with:

     
        
    docker volume create firefly_iii_db
    docker volume create firefly_iii_upload
    
    
      

    And untar your data into the volumes:

     
        
    docker run --rm \
      -v firefly_iii_db:/to \
      -v $(pwd):/from \
      alpine sh -c "cd /to && tar xf /from/firefly_iii_db.tar"
    
    docker run --rm \
      -v firefly_iii_upload:/to \
      -v $(pwd):/from \
      alpine sh -c "cd /to && tar xf /from/firefly_iii_upload.tar"
    
    
      

    Then make sure you've manually brought over the compose file and those two .env files, and you should be able to docker compose up and be in business again. Good choice with Proxmox in my opinion.

  • I'm not clear from your question, but I'm guessing you're talking about data stored in Docker volumes? (if they are bind mounts you're all good - you can just copy it). The compose files I found online for FireflyIII use volumes, but Hammond looked like bind mounts. If you're not sure, post your compose files here with the secrets redacted.

    To move data out of a Docker volume, a common way is to mount the volume into a temporary container to copy it out. Something like:

     
        
    docker run --rm \
      -v myvolume:/from \
      -v $(pwd):/to \
      alpine sh -c "cd /from && tar cf /to/myvolume.tar ."
    
    
      

    Then on the machine you're moving to, create the new empty Docker volume and do the temporary copy back in:

     
        
    docker volume create myvolume
    docker run --rm \
      -v myvolume:/to \
      -v $(pwd):/from \
      alpine sh -c "cd /to && tar xf /from/myvolume.tar"
    
      

    Or, even better, just untar it into a data directory under your compose file and bind mount it so you don't have this problem in future. Perhaps there's some reason why Docker volumes are good, but I'm not sure what it is.

  • Season 2

  • Ideas

    Jump
  • I'm local first - stuff I'm testing, playing with, or "production" stuff like Jellyfin, Forgeo, AudioBookshelf, Kavita etc etc. Local is faster, more secure, and storage is cheap. But then some of my other stuff that needs 24/7 access from the internet - websites and web apps - they go on the VPS.

  • I just do one Docker container per LXC. All the convenience of compose, plus those sweet Proxmox snapshots.

  • Is there a reason not to use Tailscale for this?

  • Forgejo - actively developed open source. It's what powers Codeberg. Easy to set up and manage with Docker. I moved to it from Gogs and skipped Gitea after reading about the forks.

  • Me in the break room stopping the microwave before the beeps:

    Here future microwave user, have these free nine seconds I'm leaving you.

    Me finding the timer is not cleared when I want to use the microwave:

    Ugh, now I have to press the reset button before I can enter the length of time to warm my lunch. Who was the accursed person who left time on here?

  • It is only resolving for devices in the Tailnet. Kuma is checking they are all up, and this Ansible playbook is checking they have all their updates. I wouldn't have thought that was an unusual arrangement - and it's worked perfectly for about a year till about three weeks ago.

  • Selfhosted @lemmy.world

    Tailscale MagicDNS issues since 1.84.1 mac?

  • Yes, this.

  • Thanks yes - that's exactly what I needed.

  • Thanks - this is exactly what I needed.

  • Yes - we're "I'll let you use my electricity for your computer thing" friends, not "I'm okay with seeing your printer on my home network" friends.

  • Selfhosted @lemmy.world

    Good experience with neko remote browser

  • Selfhosted @lemmy.world

    Bathroom scale options?

  • Coffee @lemmy.world

    Experience of the HiBREW G5?

  • Selfhosted @lemmy.world

    Beware Hollywood’s digital demolition: it’s as if your favourite films and TV shows never existed

    www.theguardian.com /commentisfree/2024/oct/01/hollywood-digital-demolition-films-tv-shows-wiped
  • Selfhosted @lemmy.world

    Selfhosted S3 compatible recommendations?

  • Coffee @lemmy.world

    Noob espresso experience (longish post)

  • Selfhosted @lemmy.world

    ‘My whole library is wiped out’: what it means to own movies and TV in the age of streaming services

    www.theguardian.com /media/article/2024/may/14/my-whole-library-is-wiped-out-what-it-means-to-own-movies-and-tv-in-the-age-of-streaming-services
  • Coffee @lemmy.world

    Are you getting good use out of your espresso machine?

  • Coffee @lemmy.world

    How are you brewing your Aeropress?

  • Coffee @lemmy.world

    New grinder. Definitely needs a few more clicks.

  • Coffee @lemmy.world

    I need help with tasting basics

  • Selfhosted @lemmy.world

    Certbot is great. Let's Encrypt is great.

  • Selfhosted @lemmy.world

    wildcard email hosting/forwarding?

  • Selfhosted @lemmy.world

    Cancelled Dropbox