tux7350

joined 2 years ago
[–] tux7350@lemmy.world -1 points 1 day ago

Thats a lot of text that didnt actually respond to my comment.

Your original statement was that ICE will snatch you up after 31 days of being awol.

Let's clarify a couple things. You are awol the second you dont show up to formation. Article 85 is desertion, the UCMJ article that you can get charged with. Theres no arbitrary amount of days, the second you're awol you could be charged with desertion. Read the Article and tell me if you see a time.

You also completely ignored the ICE comment. Your factually incorrect and fear mongering comments are unwelcome.

[–] tux7350@lemmy.world 0 points 1 day ago* (last edited 1 day ago) (2 children)

Originally you said

After 31 days, you’re not awol. The military lists you as a deserter

And I said that 31 days is nothing, to which you responded

But that’s at the CO’s discretion, but three months is nothing lmao

So which is it? I was responding to your original claim that after 31 days ICE will hunt you down and give you ten years. Which is a completely silly claim on its own, the US Marshals are in charge of finding federal fugitives.

[–] tux7350@lemmy.world 11 points 2 days ago (4 children)

Haha no, we had a boot go out for a pack of smokes and they picked him up 3 months later in a hotel in Palm Springs with two hookers. Fucker was back in morning formation with an NJP the next morning.

They spend a metric fuck ton on how to train you to do your job. They are going to get their investment back.

[–] tux7350@lemmy.world 1 points 2 days ago

Have you tried setting up qemu with virt-manager? Theres a lot of info on how to set it up for most distros and I find the GUI is very straightforward and easy to use.

[–] tux7350@lemmy.world 11 points 2 days ago (1 children)

Made me laugh in the middle of a restaurant, thanks 🤣

[–] tux7350@lemmy.world 1 points 2 weeks ago

Thank you for the laugh (⁀ᗢ⁀)

[–] tux7350@lemmy.world 10 points 2 weeks ago (2 children)

Yeah you just have to deal with mast bumping, as if thats any less worrying.

[–] tux7350@lemmy.world 6 points 2 weeks ago

You can use Authentik to setup an LDAP outpost then use a jellyfin LDAP plug-in to sync everything up.

https://github.com/jellyfin/jellyfin-plugin-ldapauth?tab=readme-ov-file

[–] tux7350@lemmy.world 5 points 1 month ago

Course, feel free to DM if you have questions.

This is a common setup. Have a firewall block all traffic. Use docker to punch a hole through the firewall and expose only 443 to the reverse proxy. Now any container can be routed through the reverse proxy as long as the container is on the same docker network.

If you define no network, the containers are put into a default bridge network, use docker inspect to see the container ips.

Here is an example of how to define a custom docker network called "proxy_net" and statically set each container ip.

networks:
  proxy_net:
    driver: bridge
    ipam:
      config:
        - subnet: 172.28.0.0/16

services:
  app1:
    image: nginx:latest
    container_name: app1
    networks:
      proxy_net:
        ipv4_address: 172.28.0.10
    ports:
      - "8080:80"

  whoami:
    image: containous/whoami:latest
    container_name: whoami
    networks:
      proxy_net:
        ipv4_address: 172.28.0.11

Notice how "who am I" is not exposed at all. The nginx container can now serve the whoami container with the proper config, pointing at 172.28.0.11.

[–] tux7350@lemmy.world 7 points 1 month ago (2 children)

Well if your reverse proxy is also inside of a container, you dont need to expose the port at all. As long as the containers are in the same docker network then they can communicate.

If your reverse proxy is not inside a docker container, then yes this method would work to prevent clients from connecting to a docker container.

[–] tux7350@lemmy.world 13 points 1 month ago (4 children)

Something like this. This is a compose.yml that only allows ips from the local host 8080 to connect to the container port 80.

services:
  webapp:
    image: nginx:latest
    container_name: local_nginx
    ports:
      - "127.0.0.1:8080:80"
view more: next ›