People talk about EVs like they do long haul 12 hour road trips every week and that it's just "imposssssible" to have an EV. Like, it's not nearly as bad as people make it sound, and then even then if it is terrible just keep an ICE vehicle around for them. Apparently I'm a weird one with 99% of my trips being commuting, going to the grocery store, random errands, and short 20ish mile drives.
scrubbles
And that's exactly what I recommend for people who can only have one car, it's not as great as a full EV, but it'll get you over the hump
This is valid, the charging infrastructure was getting much better than stalled ironically because people said "the charging infrastructure isn't good enough". If a trip is long enough sometimes we just rent a car
A prime example of the argument propaganda has pushed.
How do I know? Because I've seen this argument literally hundreds of times and it's so easily bunked.
How often do you actually make that drive? Is it every month or more? I highly highly doubt that you're driving that far that frequently.
If it's that rare? Rent a car. It'll be less than buying gas.
Or, if you have a two car household have one EV and one ice. Take the ice on long trips and then 99% of the trips you take near home it's ev.
Having a charger at home is honestly so freaking nice. I just don't think about gas or gas stations or anything. I will never go back to ICE vehicles after this one
Turns out it was never them being worried about the power usage at all...
This is technically true, but misses the context of massive PR and smear campaigns against EVs on social media. People voted with their wallet after being bombarded with propaganda on EVs being somehow more dangerous, somehow worse for the environment, and that it's more fun apparently to go to a gas station every week.
Me, an EV owner who hasn't gone to a gas station in 2 years now, has had no maintenance, and happily charges at home
They killed off openvpn support a few years ago and am glad I did. They don't care about power users, so they don't care about my money either. Good riddance
Of course! Let me know how you run your containers and I may be able to help on that side too
Sure! I use Kaniko (Although I see now that it's not maintained anymore). I'll probably pull the image in locally to protect it...
Kaniko does the Docker in Docker, and I found an action that I use, but it looks like that was taken down... Luckily I archived it! Make an action in Forgejo (I have an infrastructure group that I add public repos to for actions. So this one is called action-koniko-build and all it has is this action.yml file in it:
name: Kaniko
description: Build a container image using Kaniko
inputs:
Dockerfile:
description: The Dockerfile to pass to Kaniko
required: true
image:
description: Name and tag under which to upload the image
required: true
registry:
description: Domain of the registry. Should be the same as the first path component of the tag.
required: true
username:
description: Username for the container registry
required: true
password:
description: Password for the container registry
required: true
context:
description: Workspace for the build
required: true
runs:
using: docker
image: docker://gcr.io/kaniko-project/executor:debug
entrypoint: /bin/sh
args:
- -c
- |
mkdir -p /kaniko/.docker
echo '{"auths":{"${{ inputs.registry }}":{"auth":"'$(printf "%s:%s" "${{ inputs.username }}" "${{ inputs.password }}" | base64 | tr -d '\n')'"}}}' > /kaniko/.docker/config.json
echo Config file follows!
cat /kaniko/.docker/config.json
/kaniko/executor --insecure --dockerfile ${{ inputs.Dockerfile }} --destination ${{ inputs.image }} --context dir://${{ inputs.context }}
Then, you can use it directly like:
name: Build and Deploy Docker Image
on:
push:
branches:
- main
workflow_dispatch:
jobs:
build:
runs-on: docker
steps:
# Checkout the repository
- name: Checkout code
uses: actions/checkout@v3
- name: Get current date # This is just how I label my containers, do whatever you prefer
id: date
run: echo "::set-output name=date::$(date '+%Y%m%d-%H%M')"
- uses: path.to.your.forgejo.instance:port/infrastructure/action-koniko-build@main # This is what I said above, it references your infrastructure action, on the main branch
with:
Dockerfile: cluster/charts/auth/operator/Dockerfile
image: path.to.your.forgejo.instance:port/group/repo:${{ steps.date.outputs.date }}
registry: path.to.your.forgejo.instance:port/v1
username: ${{ env.GITHUB_ACTOR }}
password: ${{ secrets.RUNNER_TOKEN }} # I haven't found a good secret option that works well, I should see if they have fixed the built-in token
context: ${{ env.GITHUB_WORKSPACE }}
I run my runners in Kubernetes in the same cluster as my forgejo instance, so this all hooks up pretty easy. Lmk if you want to see that at all if it's relevant. The big thing is that you'll need to have them be Privileged, and there's some complicated stuff where you need to run both the runner and the "dind" container together.
But you are charged for it.
Price is the only reason that I've seen that I respect. They are more expensive. If you can afford one I recommend switching, if you can't then I understand.
No charging at home is doable, but it wouldn't be easy, so I also respect that one - but I recommend something like a plugin hybrid for when you can.
For 80% of Americans who have at least 2 cars and a garage though, there's no reason not to have one of them be an EV. You have a place to charge at home so you never need gas, and yes it's more expensive but if you have a garage and can afford more than one car, then maybe hold on for the extra 10k to get an EV.