I like the idea of the service though, but pricing is not that attractive for me currently.
Personally I think the price is high given the free alternative, but would pay it if you made some kind of security guarantees around one docker container not pwning the others, maybe you marketing can emphasize that self hosting docker containers is a footgun if you don't know what you're doing.
Re footgun: Yes, just dont want to start with fear mongering marketing :D
All the best for you and your project!
would like to see a supported Terraform provider
I built a similar in-house project like this for a client. I used the Go docker SDK and had quite a few edge cases to solve! Very curious to see if you had a similar experience.
Congratulations on launching!
I'm currently building a similar service but for 'serverless functions' (hate that terminology to be honest), so not long running containers but one off tasks. Similar to AWS Lambda and the likes.
gonna try and probably recommend your product to some friends who need this :)
I should also point out that "Docker hosting" is rather ambiguous. I had to scroll way down the page to figure out whether you are storing Docker images (like DockerHub) or running them (like ECS or fly.io).
Post-GDPR rules in the EU are clear about the Cookie Banner, providers must make it as easy to refuse cookies as it is to accept them.[1] Also, as you said, livechat cookies are definitely not required when visiting the website, but they make it impossible to opt out. I assume they cut this corner because it was too much work for them to conditionally include their livechat javascript.
If the authors moved fast and broke things on basic stuff, my first thought is "what kind of other corners did they cut when deploying/running docker?" There is a lot of security and isolation options/configuration involved when one runs docker in a secure environment, which are not enabled by default.
[1] https://www.edpb.europa.eu/system/files/2023-01/edpb_2023011...
The linked doc is 8 pages of rules about layout, placement, color, contrast, function, etc. of components in a cookie banner. Said document references (without quote or link in most cases) various EU statutes, directives, regulations, and opinions.
Even with all that, the doc carries a disclaimer that it is not to be considered authoritative and various other requirements and interpretations may also govern said banners.
Telling people that this is "clear" is perhaps you saying that you have developed an uncommon expertise in this area. For which: that is great for you.
But let's be absolutely straight about this: none of this is clear to a person who does not possess the uncommon expertise you have.
There is none really. Usually, some beginner wrote a blog post that basically says "install fail2ban" and that's how many people consider their linux server "secured". But there is much more than that. For example, "put your entire firewall to DENY, and only open what is really necessary." Or "put SSH behind spiped[1] or wireguard". Or "Harden the maximum of your systemd units"[2]. Or "don't do chmod 777, try to understand why it doesn't work." And so on and so on...
For docker, it's the same, I'm not a docker fan, as I mostly use podman, which allows to runs container as different users. In general for security, I would recommend podman running as non-root, but if you insist to run Docker, here are a few places where you could start to harden it:
* Look into enabling and enforcing SELinux policies or Apparmor profiles on your host: https://www.mankier.com/8/container_selinux or https://docs.docker.com/engine/security/apparmor/
* Look into root-less docker daemon: https://docs.docker.com/engine/security/rootless/
* Make sure you don't run any priviledged container, if you do, look into alternatives to run them in non-priviledged mode
Docker has a page about security, it looks like they echo a lot of things I'm saying: https://docs.docker.com/engine/security/ . Avoid GRSEC though, it's basically security theater. They mention docker seccomp profiles[3], which I've never used, but is definitely a good idea when hardening untrusted code.
Also, hardening the OS that you're running docker on (using the things I mentioned earlier about Linux) won't hurt.
[1] https://www.tarsnap.com/spiped.html
[2] https://ruderich.org/simon/notes/systemd-service-hardening
No, just stupid and wasn't aware. Fixing that right now!
- EU cookie banners and GDPR
- How to display prices in the EU
While both are "consumer protection regulation" they are also extra work for early startups. A good case study on how the EU bureaucracy affects a startup.
In the EU you're not allowed to advertise a price without all taxes. This means that per country you need to know the VAT % and adjust the price accordingly. You cannot change the price per EU country. You set a base price for the EU and add VAT. Since VAT differs per country this will cause non-round numbers. But this is expected.
"When you buy goods online in the EU, prices may vary from country to country or across different versions of the same website, for example due to differences in delivery costs. However, if you buy goods online without cross-border delivery – such as when you buy something online which you intend to collect from a trader or shop yourself – you should have access to the same prices and special offers as buyers living in that EU country." [1]
[1] https://europa.eu/youreurope/citizens/consumers/shopping/pri...
I am French. I could buy something for X€ in Germany, and someone in Germany would have the same price. But I can buy this for Y€ in France and Z€ in spain.
This is a common thing to do with, say, Amazon where I can buy something in Germany because the price is better and have it delivered from France to France (the delivery can also be cross-border, it depends)
tl;dr Ask US data-hoarding startups and corporations