I recently worked with a bank's offshore engineering team, and I was really surprised to discover that they had banned the use of Docker. Their setup was pretty restrictive—developers were limited to virtual desktops that didn't allow any virtualization, meaning they were completely deprived of popular tools like Docker, TestContainers, and LocalStack. They also shared a single development environment, which often caused issues since everyone was stepping on each other's changes. Given this context, how often do you see such bans in banks or similar organizations? I'm also curious about what workarounds others might be using in such environments.
5 Answers
Many large organizations, not just banks, tend to impose such bans for various reasons—whether due to the cost of licenses or internal politics around tools like Docker. It limits productivity and, quite frankly, doesn’t reflect well on their adaptability in the tech world. But I’ve noticed places finding ways around this by using Podman or working in isolated environments.
For real! Sometimes you just need to ask for a Linux environment to get around the restrictions.
Banning Docker seems to stem from risk management. Financial organizations face relentless audits, and introducing new tools raises countless questions about compliance. It's often safer, in their minds, to stick with minimal tech and manage what they already have instead of incorporating something new and complex.
Yup! They want to avoid audits discomfort at any cost, even if it means sacrificing development speed.
For sure! That cautiousness does backfire sometimes, leading to inefficiency and developers feeling stuck.
Yes, this kind of restriction is quite typical in the banking sector. They have layers of regulations and a culture that resists change, focusing heavily on security. In my previous job at a bank, we couldn’t use any modern tools easily—everything was heavily monitored, with limits on what software we could access. It feels like regressing back to outdated practices.
It's pretty common, especially in banks. Many organizations think they can't use tools like Quarkus due to Docker restrictions, but you can often run them without Docker. Alternatives like remote Docker setups or virtual machines are also options, but many banks stick to their restrictive policies without considering changes to allow Docker.
You might also want to consider alternatives like Podman or LXC if they're banning all containerization.
Just to add, while Quarkus is great, it's not the only technology that's usable without Docker; many Java frameworks work fine too!
True, especially in security-focused firms. These bans can lead to a drop in productivity and frustration among developers. Sometimes, the good engineers leave because of such constraints, while others are stuck navigating a labyrinth of outdated policies.
Absolutely! Audits in banks are a nightmare. They prefer to play it safe rather than risk the headache of convincing auditors why they've allowed certain tools.
Exactly, even if they implement Docker, the concerns around security make them overthink everything. It's just easier for them to ban it.
Exactly, many companies simply resort to using Podman as an alternative. It’s about finding creative solutions within the limitations.