• 0 Posts
  • 11 Comments
Joined 1 year ago
cake
Cake day: June 21st, 2023

help-circle
  • I’ve always hated it and thought it was a stupid untuitive mechanic that didn’t map to anything in real life. It also looks equally stupid in multiplayer when you see player character models spasm their way up a ledge during a crouch jump. It’s an old school mechanic that I am glad is going out of fashion due to better vault controls.

    like a simulation of pulling your legs up in real life.

    You don’t pull your legs up in real life though, you use your hands to vault onto something. You can’t just swap stances in mid air without holding onto anything. Even if you were talking about box jumps, like the kinds you normally do at a gym, it still isn’t anything remotely like a crouch jump. Also anyone doing a box jump in an actual combat situation just looks goofy.

    Any time a game explicitly has a tutorial for crouch jump, my immersion is completely broken. I am instantly reminded that it is a game.






  • Definitely not necessary. If that was the case, it wouldn’t live up to it’s claims of being a transparent Docker replacement at all. I think you do need to use systemd if you want to go full rootless, but I haven’t tried it enough to make a solid call on that.

    But yeah, with the above steps, I’ve moved seamlessly over to Podman for my self hosting stack and I’ve never looked back. It’s also great because I can take literally any Docker Compose I find on the Internet and it will most likely just work.


  • Your issues stem from going rootless. Podman Compose creates rootless containers and that may or may not be what you want. A lot more configuration needs to be done to get rootless containers working well for persistent services that use low ports, like enabling linger for specific users or enabling low ports for non-root users.

    If you want the traditional Docker experience (which is rootful) and figure out the migration towards rootless later, I’d recommend the following:

    1. Install podman-docker. This provides a seamless Docker compatibility layer for podman, allowing you to even use regular docker commands that get translated behind the scenes into Podman.
    2. Install regular docker-compose. This will work via podman-docker and gives you the native docker compose experience.
    3. Enable podman.socket and podman-restart.service. First one socket-activates the central Podman daemon, second one restarts any podman containers with a restart-policy of always on boot.
    4. Run your docker-compose commands using sudo, so sudo docker-compose up -d etc. You can run this with sudo podman compose as well if you’re allergic to hyphenation. Podman allows both rootful and rootless containers and the way you choose is by running the commands with sudo or not.

    This gets you to a very Docker-like experience and is what I am currently using to host my services. I do plan on getting familiar with rootless and systemd services and Kubernetes files, but I honestly haven’t had the time to figure all that out yet.