You have a docker container running on a remote server.
Do you use
A. dev container extension in vscode and connect to that container directly
B. ssh remote extension in vscode and first connect to server then docker attach the container in the terminal panel
C. ssh only and connect directly to the server and docker attach then vim editing?
Ask in Slack what are the other people doing, chit chat a little and then also ask the bot, do what is needed and end the day early to go play StaraField. Let the timer running till end of turn and some more.
repeat till paycheck.
>plays boring dogshit AAA goyslop
>relies on AI because he doesnt understand what hes doing
>in it for the money, no actual interest in his work or field
i would kill myself if i were you
C because why would i ever use vscode?
>why would i ever use vscode?
to get employeed
im already employed without installing this worthless pile of shit?
C. I don't use vscode, besides k8s bash exec is locked behind an escalated privileges mode.
10 years without it, no one has ever said shit like "vscode or get fired".
> cant sign your commits without all this hacky shit
tfw home lab running 32 cores while running a thin client that is light as a feather
If you're routinely editing files from within a container then consider why you're doing that and whether there's a better way.
For example, could the files you're editing be stored outside the container and bind mounted in?
>If you're routinely editing files from within a container
How is that a bad thing if you are editing files on the mounted folder?
Why the fuck are you messing with containers remotely? And is right, it is literally written on docker docs.
Then you shouldn't mess with it from within the container. You are supposed to have persistence using bind mounts.
>Why the fuck are you messing with containers remotely?
not OP but a lot of container images themselves need to be tested in remote environments mirroring production
you're right that you definitely shouldn't be fucking around with files from inside the container regularly, though
Why the fuck would I need to remote into a docker container? Stop cargo culting. If you don't have so many containers that individually maintaining them is not a viable solution then you don't need Docker.
>If you don't have so many containers that individually maintaining them is not a viable solution then you don't need Docker.
Not sure I agree. Docker is very useful for hosting individual single-server services as well. You still shouldn't be remoting into one except for debugging, of course, being a normally sealed box is the whole point of a container.
>Not sure I agree. Docker is very useful for hosting individual single-server services as well.
If you only have one hosted service you ABSOLUTELY should not be using containers.
And debugging in production by stepping through the production deployment? Holy shit, how old are you? What back water hick service do you operate?
>If you only have one hosted service you ABSOLUTELY should not be using containers.
Why?
>And debugging in production by stepping through the production deployment?
No, that's not what I meant. I'm talking about things like figuring out what the fuck went wrong on production on some freak error when the logs aren't being helpful and you have the fish the relevant traces out of the pod somewhere.
I'd probably go for a personally hosted VPN, then run code-server on the server
i use b even though it litters the workspace with sketchy folders
A
>hey, you know trendy framework that big important people use?
>what's the best way to use it in such a way that demonstrates that you completely don't understand its use case
>should I use VS Code extension or should I just use the command line through VS Code
nu devs I swear. any time I see someone advocating VS Code I'll think of you
Neither, testing is done locally and production and UAT containers are immutable, nobody is allowed to connect
A because i want to get shit done
I'm going to hijack this thread to ask you Docker-chads how do you update all your docker containers at once.
For example, I have multiple docker-compose.yml files running on my servers.
How do I easily update them all without needing to run commands for each individual yml file?
find with exec
Just write a bash script