Not

Hacker News!

Beta
Home
Jobs
Q&A
Startups
Trends
Users
Live
AI companion for Hacker News

Not

Hacker News!

Beta
Home
Jobs
Q&A
Startups
Trends
Users
Live
AI companion for Hacker News
  1. Home
  2. /Story
  3. /Ask HN: How common is banning Docker?
  1. Home
  2. /Story
  3. /Ask HN: How common is banning Docker?
Nov 14, 2025 at 7:36 AM EST

Ask HN: How common is banning Docker?

martypitt
9 points
12 comments

Mood

calm

Sentiment

negative

Category

other

Key topics

Docker

Devops

Enterprise-Software

Virtualization

Debate intensity40/100
I was doing some client work recently at a bank, where most of their engineering is offshored one of the big offshore companies.

The offshore team had to access everything via virtual desktops, and one of the restrictions was no virtualisation within the virtual desktop - so tooling like Docker was banned.

I was really surprsied to see modern JVM development going on, without access to things like TestContainers, LocalStack, or Docker at all.

To compound matters, they had a single shared dev env, (for cost reasons), so the team were constantly breaking each others stuff.

How common is this? Also, curious what kinds of workarounds people are using?

The author describes a restrictive development environment at a bank where Docker was banned, and asks how common such restrictions are and what workarounds others are using.

Snapshot generated from the HN discussion

Discussion Activity

Active discussion

First comment

5m

Peak period

12

Day 1

Avg / period

12

Comment distribution12 data points
Loading chart...

Based on 12 loaded comments

Key moments

  1. 01Story posted

    Nov 14, 2025 at 7:36 AM EST

    11 days ago

    Step 01
  2. 02First comment

    Nov 14, 2025 at 7:41 AM EST

    5m after posting

    Step 02
  3. 03Peak activity

    12 comments in Day 1

    Hottest window of the conversation

    Step 03
  4. 04Latest activity

    Nov 15, 2025 at 6:30 AM EST

    10 days ago

    Step 04

Generating AI Summary...

Analyzing up to 500 comments to identify key contributors and discussion patterns

Discussion (12 comments)
Showing 12 comments
galaxy_gas
11 days ago
1 reply
If they run in one dev env, (for cost reasons), it is preferably in Docker is VERY expensive if you are not using it for personal, noncommercial usage now ...

VDI VM in VM often not ideal aswell,

Docker is paid per seat monthly subscription for commercial usages

martypitt
11 days ago
The block was not for docker license cost reasons - it was part compliance, and part an issue with the underlying VDI VM they were using.

The onshore team were able to use Docker, but not offshore.

anovikov
11 days ago
1 reply
It is not common and as you could have figured from the rest of this arrangement, it's just yes, this organisation is broken. Which is usually a good thing, broken places are usually to make money off that's why they remain broken for a long time - some places might go under because of that, but not a bank.
7bit
11 days ago
1 reply
Banning docker equals to broken company to you? Please, have your opinion, but dont run around spreading absurd claims...
anovikov
10 days ago
No, it is the fact that they outsource their IT to the lowest bidder and surround their work with ridiculous limitations our of the false hope of savings, that both destroy productivity, and make accountability impossible.

It's fine, many large orgs are like this.

Bender
11 days ago
1 reply
I was doing some client work recently at a bank

Having worked for a bank I will add my jaded opinion. Throw logic out of the window. Banks have their own regulations, history and internal policies. Finding a job is hard right now so one may have to grin and just accept it. Don't think too much about it.

Ask them if you can use VMWare or VirtualBox in the virtual desktop and get a VMWare license assigned to you. It's clunky but something they might actually have and may save some headaches. If this is an option ask them which Linux ISO is permitted and where it is.

How common is this?

Very common for a bank especially for offshore or remote employees.

Also, curious what kinds of workarounds people are using?

Nobody outside of the bank will like this answer. Ask them what work around is permitted within the policy. If your questions are always without emotion and always centered around policy they may grow to like you and with time you may earn more trust than others making your job just a little easier.

martypitt
11 days ago
Thanks!

I've finished up there now, so this is purely retrospective.

For them - the workaround (sadly) was -- a lack of testing.

I was really surprised that in a heavily regulated environment (this project faced off to a regulator) Integration testing (which has gotten really easy on the JVM thanks to stuff like TestContainers) just didn't exist.

That could be symptom of a broader lack of a test-driven culture though.

scaredreally
11 days ago
1 reply
Every environment is a copy of the data, I would imagine. I think you would want to limit spawning of copies of your data in an offshore outsourced environment for security reasons. That's my guess.
antonymoose
11 days ago
Having worked in HFT, we had contractual obligations imposed on us by our customers for this very reason. In our case it wasn’t the data but rather the source code that we sold on to a few large banks that they were concerned for.
apothegm
11 days ago
It might just be an unintentional side effect of an older rule. They don’t want people running full-on nested VMs probably due to security concerns (inability to properly lock down the nested VMs). They wrote that rule in, say, 2005, and haven’t revisited it since the emergence of containerization as a best practice. Possibly because like most banks their software practices lag by decades.
aitchnyu
11 days ago
I was in an Indian service company and worked for Indian and US branches of a company. The regulations were high, employees know more stuff and people and *carve out* a streamlined workflow, we contractors have to obey the rules literally, our feedback are Chinese whispers (me, my manager, their manager...) and we have to fend for themselves.

For specific stories. We had Windows virtual desktops. Our unit test suites assume an Unix environment like the employees Macs or Jenkins, so we had to coax Jenkins to run our feature branches and there may be 12 hour waits for our builds. We also had to plan leaves around their quarterly plans and hard deadlines while they they never treated quarterly plans as deadlines or cycles. Debugging with client is affected by timezone differences too.

jakepage91
11 days ago
Just out of curiosity, what does the dev env look like? A set of VMs? K8s? If k8s, then mirrord for teams can be useful for testing code locally against the dev env dependencies without having to containerize while also not breaking the shared env dependencies for others.

Disclaimer: I work for the parent company

View full discussion on Hacker News
ID: 45926181Type: storyLast synced: 11/16/2025, 9:43:00 PM

Want the full context?

Jump to the original sources

Read the primary article or dive into the live Hacker News thread when you're ready.

View on HN

Not

Hacker News!

AI-observed conversations & context

Daily AI-observed summaries, trends, and audience signals pulled from Hacker News so you can see the conversation before it hits your feed.

LiveBeta

Explore

  • Home
  • Jobs radar
  • Tech pulse
  • Startups
  • Trends

Resources

  • Visit Hacker News
  • HN API
  • Modal cronjobs
  • Meta Llama

Briefings

Inbox recaps on the loudest debates & under-the-radar launches.

Connect

© 2025 Not Hacker News! — independent Hacker News companion.

Not affiliated with Hacker News or Y Combinator. We simply enrich the public API with analytics.